SLA targets(WS:4.3.1)
VisualSLA targets are your organization's own answer to "how long may this kind of issue take?". Each target names an issue type and either all projects or one project, and gives a number of calendar days, counted from the moment the issue was created until it first reaches a status your Jira reports as complete.
Questions this can help answer
- Which issue types does the SLA breach page measure, and against how many days?
- Which projects have a target of their own, and which follow the all-projects target?
- How many open issues would a target apply to, and how many are already past it?
How a target is chosen for an issue
- A target for the issue's project and type takes precedence over a target for all projects and that type.
- An issue whose type has no target gets no SLA state: it is never shown as on track, at risk or past its target.
- Two targets for the same project and type cannot exist side by side; change the existing one instead.
Under each target, a line says how many open issues it applies to today and how many of them are already past it, so the effect of a change can be read before it is saved.
Who can change them
Every member can read the targets. An owner or an admin can add, change or remove one, or adopt MetaFrazo's suggestions (5 calendar days for bugs, 10 for stories, 30 for epics, 7 for any other type) as the organization's own starting targets in one step; the suggestions are never applied without that step. Every change is recorded with who made it, when, and the value before and after.