nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to get smart value for status change date?

Rupali Choudhari

I have automation will run for tickets which will move from ‘status A’ to 'status B', based on severity.The SLA due date is calculated based on current date + business days (7, 30, 90 or 180) based on severity (P0,p1.P2,P3) respectively.

if I re-assign the Severity let's say from P0 to P2, the due date doesn’t re-calculate. The desired behavior would be if we change the severity the due date should re-calculate based on the new business days. For this scenario, we would still use the original status B date as the baseline.

How do I get date of Status B to calculate the new SLA due date?

I want to get some Jira smart value like {{issue.statusB.date}} ?

Accepted answers

Kevin Christmann_v58psw

@Rupali Choudhari What about the following...

1. Trigger = change on severity

2. If else statements where you check for P0 through P2

3. Within each of those blocks you can then try an edit on your Date field and set it using a smart value to something similar to this {{issue.customfield_12345.plusDays(numberOfDays.asNumber)}}

(I don't know the actual custom field value you have, and of course whatever days you want for P0 through P2.

All comments

Kevin Christmann_v58psw

@Rupali Choudhari What about the following...

1. Trigger = change on severity

2. If else statements where you check for P0 through P2

Rupali Choudhari

Thanks for your suggestion.

Let me give a try to above solution .

Kateryna_v_SaaSJet_

Hi @Rupali Choudhari

If this is still relevant to you, I can suggest several solutions, but they are all based on SLAs for individual statuses. If you don't mind using third-party apps, I'll show how it would look like in SLA Time and Report for Jira.

For each SLA, one status must be set to Start and all other statuses to Stop. Here are a few options for counting the time until your trigger: until the Negotiated date (according to your custom field) or count a specific Time limit of hours (days) from the start of the SLA.

In the case of the Negotiated date type, the value will be taken from your custom field of each task.

In the case of a Time limit, you specify a specific time before violation that will be universally applied to each task.

Maybe it sounds complicated, but if you are interested in the add-on, then book an online demo. My team developed this app, so we will help you with the settings if needed.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud