Plan requirement
| Subscription | Any plan |
| Access | Admin |
Linking tickets to development issues. The most useful integration most support teams install, and the one with the most process attached.
Connect it
- Install the integration in Admin Center.
- Authorise it against your Jira.
- Choose which projects and issue types are in scope.
- Decide what is synchronised in each direction.
- Test with one real ticket and one real issue.
Agree the process before the settings
Who may create an issue from a ticket, what has to be established first, and what happens when the issue is closed. Without that, support creates issues nobody triages and the connection produces resentment on both sides.
This is the part that decides whether the integration works, and it is not a configuration question.
Link many tickets to one issue
Ten customers reporting the same bug is one issue and ten links. Creating ten issues buries the development team and hides how many customers are affected.
Searching for an existing issue before creating one is the habit worth teaching.
Decide what comes back
A status change on the issue can update the ticket. That is the half agents care about, because it is how they know to tell the customer.
Do not sync comments blindly
Internal development discussion is not written for customers, and support tickets contain customer detail developers do not need. Choose deliberately what crosses.
Authorise with an account that stays
Not a personal one. When that person leaves, the connection breaks, and it fails quietly.
Watch the volume
If support creates many issues that are never picked up, that is worth raising as a process problem rather than accepting as normal.
Comments
0 comments
Article is closed for comments.