JIRA Service Desk existing issues breached SLA

I'm probably doing something wrong here but can't figure out what.

When applying JSD to an existing project the reports for Breached vs Met show that every single issue prior to the application of JSD has breached it's SLA. I've set up the calendars and goals to reflect our SLA's and re-indexed the instance however the reports remain the same. No amount of tinkering seems to change this.

 

Is this supposed to happen? From my reading it seems that not applying SLA to issues previous to a change in metric is intentional, but from the first set up of JSD against a project seems counter-intuitive, especially if displays everything as "Breached". Is there any way I can get round this?

 

1 answer

This could be due to this bug reported here: https://jira.atlassian.com/browse/JSD-1512

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted 13 hours ago in Jira Service Desk

Looking for anyone who has switched from Zendesk to Jira Service Desk

Hi Community! The Jira Service Desk marketing team is looking for customers who have successfully switched from Zendesk to Jira Service Desk!   We’d love to hear your thoughts on the pros and ...

18 views 0 1
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you