SLA All remaining issues

[Ian Robinson]

Hi,

We want to restrict SLA counting against certain issue types, I believe I corrected this by setting the JQL to point to specific issuetype and matching priority.

What I have found is that the 72h All remaining issues applies the SLA to any issue type.

I applied (as seen below) what I belive was a restrictive policy by using issuetype != and confirming the issue I dont want the SLA against.

This has not worked and we are still seeing the SLA against the issue type we dont want.

[Ian Robinson · Accepted solution]

Worked it out, someone had edited the plans that were working for a while now and put a time against 'all remaining issues'

set this to 0h and now its not applying to the other issues.

[Ian Robinson]

Its not typo related as it searches and presents the options when entering the JQL, so I type 'DA -  ' then select the issue I want.

I have set issuetype = "DA - KBA Request" with 0h and this has worked.

Its not a clean workaround though, as it means I need to enter every Issue type and set to 0h so the SLA does not apply.

So I am still looking for the best fix to apply the SLA ONLY to a chosen ISSUE Type.

[Marc - Devoteam]

Hi @Ian Robinson 

My experience, let me use only to use equal to JQL on SLA's

As your screen shot shows the No target SAL applies to all issue type except "DA - KBA - Request"

But are values you set on in the JQL, the types specified Request Types in the portal or Jira Issue Types in the system.

Because if they are Request Types, you might have used the wrong name in the JQL.

Can you share your issue type in Jira (screenshot)

[Ian Robinson]

sorry Marc, I didnt reply directly to your comment