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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Jun 14, 2018 in Jira Service Desk

How the Telegram Integration for Jira helps Sergey's team take their support efficiency to the bank

...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...

531 views 3 5
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