You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We currently use these two services. The customer reports the problem to us through a portal that supports Jira service management. In it, based on priority, we have specified Sla.
A ticket is then sent via transit to the DEV team, which maps the fields from JSM and completes them in the ticket on JS.
However, we cannot find an option for the Sla to also pass between projects and be merged.
I therefore have a question as to whether there is an option to make the SLA that is displayed to us in the JSM project also visible in the JS request.
SLA is a concept of JSM and not of JSW so the SLA fields/concept is not available on a Jira Software project.
You could look in to setting the due date of the JSW issue based on the SLA target date but it's going to be tricky since it can change with the calendar of the SLA.
Imho, the Dev ticket should just be a linked issue to the JSM ticket so the SLA remains in place and the developper can always review the SLA in the linked JSM ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.