Transfer of SLA field from Jira service management to Jira software

[Marcin Klimczuk]

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.

[Dirk Ronsmans · Accepted solution]

@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.

[Michal Patoprsty]

If anyone is still looking for a way to achieve this, we have recently released an app on the Marketplace called Linked SLA Panel

It allows you to display SLA targets from linked JSM work item/ issue directly in Jira Softwar without any additional accounts, automation, or custom fields needed. Just configure the desired link type name during the initial setup and you're good to go.

Hope this helps someone who runs into the same limitation! Let me know if you’d like to see how it works.