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

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published Mar 09, 2018 in Jira Service Desk

E.L. Fridge's take on education, Jira Service Desk, and creative Jira use cases

...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...

968 views 2 14
Read article

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