The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Image of the Day: Linking Jira Service Management Requests to Jira Issues

linking-use-case.png

Concept Relates To

Application Type

Jira Work Management, Jira Software, Jira Service Management, Jira Core, Confluence

Deployment Type

Jira Cloud, Jira Server, Jira Data Center

What is shown?

The process of linking a Jira Service Management request to a dependent Jira issue and some related Confluence pages.

What can we learn?

Here’s a question I get asked a lot. “If we adopt Jira Service Management, how do we manage those requests in conjunction with other Jira issues?” It’s easier than it sounds! Here’s a diagram describing the relationship between all the elements.

Common Use Case

diagram1.png

A customer reports a problem to the customer service team, which creates a support issue. The service rep researches the issue and learns a fix is needed from the development team.

diagram2.png

The service rep create an issue in the development team’s Jira project and links it to the support request. Then the rep notifies the customer that someone is working on their problem.

diagram3.png

Next, the development team deploys their fix and closes their Jira issue.

diagram4.png

Now the service rep can tell the customer their problem is remedied and close the dependent support request.

diagram5.png

Depending on the circumstances, the service rep might add an FAQ page to the knowledge base or the developer might add a page to the documentation describing the change.

diagram6.png

Those Confluence pages should be linked to the Jira issues they relate to.

diagram7.png

Cross links may also be warranted, depending on the content’s intended audience.

Another Example

Here’s a change request in a Service Management project. It’s related to a large initiative in a software development project.

change-request.png

This change request will remain in its current status until the development team is done with their implementation work.

It’s very common for work from one team to depend on work from another. As long as the elements are linked together, it’s easy to find, detect, and even automate steps in any team’s process.


Back to intro and image list

0 comments

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

TAGS
AUG Leaders

Atlassian Community Events