Hello Atlassian Community,
My company has both Jira and Jira Service management in our environment. JSM is used as our main ITSM tool and is how customers reach out to the IT teams for their needs. Jira is used for individual teams (Infrastructure, ERP, etc.) to track long term project work they are completing.
This works well, except for when a custom requests something in JSM, that needs to be converted into a project as it is a large ask. We move the ticket to a Jira project and the customer losses visibility to it.
I'm curious, how do other companies handle these types of situations?
How do you use Jira for tracking project work internally, while still being able to provide visibility to a customer? (Something that seems to be only possible in JSM)
@Jeremy Wood The easiest way to ensure that they do not loose insights into the work item is to Clone it and leave the JSM work item in place. You can then create an automation that will move the status of the JSM work item and even provide updates based on the information of the Jira work item in the project. I have done this in the past at a different company that I worked at and it worked well.
That makes sense, but does open a couple of questions.
1. How do you manage SLA's on the JSM ticket?
2. As we have multiple Jira projects for each team, would we have to create the automation rule in each project to update the JSM ticket?
3. Digging into the automation, how do control you when to run the automation and what tickets to update?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.