Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
panelIconIdatlassian-light_bulb_on
panelIcon:light_bulb_on:
panelIconText:light_bulb_on:
bgColor#FFFAE6

Before you startbegin: Each interval between a consecutive SLA start and end point within an issue's lifespan is defined as a cycle. By default, each cycle starts with the earliest start point and earliest end point.

...

Important: After meeting the first end condition, your SLA will not restart, even if you provide a start condition after the initial end condition!

panelIcon
Panel
panelIconId4d9b059c-74f0-40da-87b2-3bc955c624ca
:einstein:
panelIconText:einstein:
bgColor#F4F5F7

For example:

Let's assume that your SLA will start when the status is To Do and end when the status is Done. Once you move the issue to To Do, your SLA will start counting until providing the end condition on this issue. When your status is Done, your SLA will never start again.

⭐ Even if you move the issue from Done to To Do, your SLA will not start, and Time to SLA will not take other cycles into account.

...

After meeting the end condition, if you provide the start condition again, Time to SLA will invalidate the previous cycle and your SLA will start again.

Panel
panelIconId4d9b059c-74f0-40da-87b2-3bc955c624ca
panelIcon:einstein:
panelIconText:einstein:
bgColor#F4F5F7

For example:

Let's assume that your SLA will start when the status is To Do and end when the status is Done. Once you move the issue to To Do, your SLA will count until it provides the end condition on this issue.

⭐ When you move the issue Done to To Do, your SLA will reset the elapsed duration and start from the beginning.

...

After meeting the end condition, if you provide the start condition again, your SLA will resume without resetting the elapsed duration.

:einstein:
Panel
panelIconId4d9b059c-74f0-40da-87b2-3bc955c624ca
panelIcon
panelIconText:einstein:
bgColor#F4F5F7

For example:

Let's assume that your SLA will start when the status is To Do and end when the status is Done. Once you move the issue to To Do, your SLA will count until it provides the end condition on this issue.

⭐ When you change the status of the issue from Done to To Do, your SLA will resume on the previous elapsed duration. Please keep in mind that the elapsed duration will not continue to count between the end and start conditions.

...

After meeting the end condition, if you provide the start condition again, your SLA will resume without resetting the elapsed duration.

panelIconId
Panel
4d9b059c-74f0-40da-87b2-3bc955c624ca
panelIcon:einstein:
panelIconText:einstein:
bgColor#F4F5F7

For example:

Let's assume that your SLA will start when the status is To Do and end when the status is Done. Once you move the issue to To Do, your SLA will count until it provides the end condition on this issue.

⭐ When you change the status of the issue from Done to To Do, your SLA will resume on the previous elapsed duration. Please keep in mind that, that unlike the All Cycles method, the Largest Span also takes into account intermediary statuses.

...

Panel
panelIconId1f371
panelIcon:bento:
panelIconText🍱
bgColor#C0B6F2

The anatomy Anatomy of an SLA panelPanel