Creating Jira Issues
Full Version Only
This page tells you what Git-Zen sends to Jira when an agent creates, links, or edits an issue. For the general steps, see Creating and Linking Issues.
The Git-Zen screens for Jira say “issue” and “label”, the same as Jira.
Create an Issue
Section titled “Create an Issue”Click Create on the Git-Zen menu bar. The Create issue window opens. Select one of the projects that you enabled on the Webhooks screen.
Issue type
Section titled “Issue type”Git-Zen creates every issue with the issue type Task. You cannot choose another type. The project must have the Task issue type. If it does not, Jira rejects the issue.
Title and description
Section titled “Title and description”Git-Zen fills in the title from the ticket subject. It fills in the description from the latest ticket comment, or from your custom default description or body format.
The description supports Markdown. Git-Zen converts it to Jira formatting, such as headings, bold, lists, links, and code blocks.
Git-Zen adds the reference tag, for example gz#12345, at the end of the description. If you turn on Add hyperlink under “Zendesk Hyperlink within issues”, Git-Zen also adds “(created from Zendesk ticket #12345 — link)” to the description. Jira has no separate “Links” entry for the ticket.
Fields
Section titled “Fields”You choose which fields show, and which are required, under “New issue fields” in the settings.
| Field | What Git-Zen does |
|---|---|
| Labels | Adds the labels. The list shows every label on your Jira site. Jira labels are global, not per project. |
| Assigned To | Assigns the issue. Jira allows one assignee. The list shows up to 50 users who can be assigned in the project. |
| Priority | Sets the Jira priority. See the table below. |
| Due Date | Sets the Jira due date. |
| Estimate | Has no effect at this time. |
| Status | Has no effect at this time. Jira starts the issue in the workflow’s first status. |
The Priority drop-down list uses fixed names. Git-Zen maps them to the standard Jira priorities:
| Git-Zen | Jira |
|---|---|
| None | (Jira default) |
| Urgent | Highest |
| High | High |
| Normal | Medium |
| Low | Low |
Not available on Jira
Section titled “Not available on Jira”These features of other platforms do not show for Jira:
- Issue templates
- Attachments
- Parent issues and related issues
- Custom fields
- Sprints and fix versions
When Jira rejects an issue, Git-Zen shows “Failed to create issue. Check the server logs for details.” You cannot see these logs. Check the project’s issue types, required fields, and priorities, then contact support if the problem stays.
Link an Existing Issue
Section titled “Link an Existing Issue”Click Link on the Git-Zen menu bar. Select the project, then the issue. The list shows up to 100 open issues. See Issue Statuses.
Git-Zen adds the reference tag to the end of the issue description. If the description is empty, Git-Zen writes “Linked to Zendesk issue” before the tag. If Add hyperlink is on, Git-Zen also adds “(related to Zendesk ticket #12345)” with a link to the ticket.
Edit the Labels of a Linked Issue
Section titled “Edit the Labels of a Linked Issue”Turn on Allow existing issue label editing under “Enable Git-Zen Features” in the settings. It is off by default. An agent then sees a pencil icon next to the labels of a linked issue.
The agent selects labels and clicks Update labels. Git-Zen replaces the issue’s labels with the selected ones. Git-Zen keeps only labels that already exist on your Jira site.
Comment on a Linked Issue
Section titled “Comment on a Linked Issue”Click the comment icon next to a linked issue. Git-Zen posts the comment as the OAuth user. The comment starts with “Agent comment from agent name in Zendesk ticket #12345:”, with a link to the ticket. Markdown is supported.
Unlink an Issue
Section titled “Unlink an Issue”When an agent removes a linked issue, Git-Zen removes the reference tag from the issue description. It does not delete the issue. It does not remove the “created from” or “related to” hyperlink text.