priority change SLA impact

IN JIRA service desk i faced an issue:-

1. Incident was raised as S2 and SLA response time was 30 m.

2. But as per analysis and discussion with customer we changed it from S2 to S3, ideally response time should have changed to 10h.

But it had not happen.

Please suggest!

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote

Hi @sunita yadav,

Please, make sure this Response Time SLA is not completed. An SLA can't be changed if it's completed. Check the goals configured to verify if the JQL is correct.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Agree that is the first step. Check the history and see if the time of sev change was not greater that time of creation +30m

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Was this helpful?

Thanks!

Jira Service Management

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

priority change SLA impact

1 answer

Comments for this post are closed

Was this helpful?

Thanks!

TAGS

Atlassian Community Events