Create
cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 
Sign up Log in

How to control Security fix for Development dep. with the SLA

My colleague from the SaaSJet team showed me an interesting solution of how it is possible to control security project tasks that were already created and didn't have any particular types or labels. Now I wish to share it with you.

1-gif take a look at new use case.gif

In this article, I describe the case in the first person, precisely as a colleague told me.

We had security tasks as requests from clients on the security project, but they were simply created as tasks without a special type, label, etc. 

I made a security_requests type for them.

The time has come when I need to calculate the SLA for these tasks, but if I put this type in Start, then the required tasks will be missed because I put the type already after their completion.

Now, in order to count them, I need to download all the tasks and look for the right type among them.

At first, I thought of setting up something in the configurations, and then I realized that some kind of filtering on the grid for a certain field would be enough for me.

How it can be done with SLA Time and Report add-on:

1. We make a task filter with JQL: issuetype = "Security request"

0-advanced filter for sedurity type issues.png

2. We create SLAs for each priority. For example, to close the task in 8 hours, if Priority= High, the conditions will be as follows:

Start  
Priority: High
Issue Type: Security request
Pause
Status: On hold
Stop
Status: Done

3. Here, is still possible to choose what is more necessary or add 2-3 more SLA configs for different statuses and then add these created SLAs to the report table.

*eventually, we changed it to our current conditions:

3-added conditions for the SLA.png

If there is a Priority table, it is possible to focus on the time limits for each of them - Highest, High, Normal, Medium, Low, etc.

3-levels-of-request-priority.png

Created 1 SLA for the test, added there:

Highest = 2 hours

High = 4 hours

Normal = 8 hours

Medium = 24 hours i.e.

Then we go to the report table and select the created SLA. Everything works!

2-sla report for security requests.png

This is just one case of using the SLA Time and Report for Jira add-on, but you will find many more on our Confluence documentation page. If you want to do the same, use the 30-day trial of the app.

πŸ™‚πŸ‘ Like from you if it was helpful. 

1 comment

Comment

Log in or Sign up to comment
Vikrant Yadav
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 2, 2023

Very Helpful @Kateryna_v_SaaSJet_ Thanks a lot!

Like β€’ Kateryna_v_SaaSJet_ likes this
TAGS
AUG Leaders

Atlassian Community Events