I moved 38 tickets from a Jira project to a JSM project. SLAs did not exist in the Jira project. However, once I moved to tickets to JSM and mapped their statuses and issue types most of the tickets began to populate the SLAs (which I was hoping for). I am wondering what to look for to determine why the other tickets aren't populating SLAs.
Hi @Jacquelyn Maly and welcome,
Please take a look at this post,
It will give you the ability to recalculate the SLA's of selected issues.
This can have multiple reasons, but mainly based on the goals set in the SLA's
Issue type not correct, status not correct, etc...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The SLA is set the same for both issue types. There are only 2 issue types. I have it set to start counting "issue created" and finish counting when it's entered a certain status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could it be because some of the issues moved were mapped to the status that stops the SLA?
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.