Edition: Enterprise



Sync a ticket with Jira

If you have followed the steps outlined in the Jira Integration page, you will find the following “Sync with Jira” section on the right hand side in the ticket page. If the Jira section is not in a convenient spot, you have the option to reorder the right hand menu of new and existing tickets.

If you have multiple Jira instances defined, you can hover over this section and the Jira Instance which the ticket is linked to will be displayed. The Jira instance is made automatically based on the Product selection that was made on your ticket. If there is no product selected on the ticket, the Default Jira Instance and Default Project Key will be used. Click here to learn more about configuring your Products for Jira.

Creating a New Issue

Clicking in the “New Issue” button will add the ticket to the queue to sync and the Issue Key will display “Pending…”. When this process is complete, the box will change from “pending…” to the Jira ticket number with a link.

A new Jira Issue will be created and a remote link to the synced TeamSupport ticket will be added in the new issue.

Linking an Existing Jira Issue

Clicking in the “Existing Issue” button will allow you to enter the Issue Key to sync with:

Enter the key and click on the Save button. The Issue Key will be displayed in black font without a link to Jira. Once the sync has taken place a new remote link will be added to the synced Jira Issue and the Issue Key in TeamSupport will become a link to the Jira Issue.

Updating Data

Once a sync has been made, if you need to make a change to the Product selection, you will be prompted to first remove the Jira sync from the ticket.

Jira Issue changes in the mapped fields listed on the Jira Integration Page will be applied to the TeamSupport ticket and new comments will generate new actions. New actions in the TeamSupport ticket will generate their equivalent new comments in the Jira Issue.

The synchronization runs every 15 minutes. Wait for at least 15 minutes after saving. Once it is done you should be able to refresh your ticket and see the updated data.

Removing a Ticket sync to Jira

You may click the “x” at any time next to the sync in order to remove the link to Jira.

Logging

Jira errors are logged in the Ticket History. Ticket History can be found on the Ticket Detail Page by clicking More -> Ticket History.

Additional logging can be found in our Reporting Section.

Automating the Ticket Links using API

TeamSupport offers an API which allows customers to have access the their TeamSupport data from outside of TeamSupport. You may use the API to set an existing Jira ticket link, or to create a new one.

The <JiraKey> element will be used to set or update the Ticket-Jira link. It is not case sensitive.

The value for it can be either the existing Jira issue key to link to the ticket to or to create a new Jira issue from the ticket using the value “NewJiraIssue” (not case sensitive, without quotes).

Existing ticket example

PUT: [API URL]\Tickets\1234
Body: <Ticket><JiraKey>TEST-12</JiraKey></Ticket>

This would set the link for ticket 1234 to a Jira issue with key TEST-12

New ticket example

PUT: [API URL]\Tickets\5678
Body: <Ticket><JiraKey>newjiraissue</JiraKey></Ticket>

This would set the link for ticket 5678 to create a new jira issue.

These commands would also work with the (POST) verb.

These commands will work with both xml or json formats. It can be combined with the other Ticket elements like any other normal element.

Click here to learn more about our API and see other example API commands.

Need more help with this?
Don’t hesitate to contact us here.

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.