Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Transfer of SLA field from Jira service management to Jira software

Marcin Klimczuk
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Mar 31, 2023

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.

1 answer

1 accepted

2 votes
Answer accepted
Dirk Ronsmans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 31, 2023

@Marcin Klimczuk ,

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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events