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; } } }

Auto Transition rule

unknown

Hi all. So I've just started with a new company and I'm trying to help organize their existing Jira instance. what i would like to do is this...

I would like to set up a trigger that will auto transition a ticket to "Closed" if it has been in the "Resolved" state for more than a set period of time. Either that, or have all "Resolved" tickets auto transition to "Closed" at the beginning/end of the month.

I figure that the latter would be an easier rule to create, but I'm not sure how to go about it. I was able to do this at my previous company, but that version of Jira was heavily modified and run internally. Any and all help on the matter would be GREATLY appreciated!

Accepted answers

Dirk Ronsmans

Hi @[deleted] and welcome!

There is actually a best practice for that. It includes an SLA so you can define a calendar with only business days to count and an automation rule.

You can find all the details here:

https://support.atlassian.com/jira-service-management-cloud/docs/auto-close-incidents-after-they-are-resolved/

If however you really want it to be at a fixed day (first/last day of the month) you'll have to create an automation rule with a JQL to find all the right issues. I'm less a fan of that as it would mean some issues remain open longer or shorter than others and this kind of rule you would like to keep standardised.

All comments

Dirk Ronsmans

Hi @[deleted] and welcome!

There is actually a best practice for that. It includes an SLA so you can define a calendar with only business days to count and an automation rule.

You can find all the details here:

https://support.atlassian.com/jira-service-management-cloud/docs/auto-close-incidents-after-they-are-resolved/

unknown

Hi Dirk,

Thanks so much for the quick response. I don't see that we have an SLA in the Project Settings. Is that something that I would need to talk to our rep about?

Dirk Ronsmans

Jikes, SLA would be a JSD/JSM feature

On JSW (Software) you should however be able to do the same just with an automation rule.

You can create a scheduled trigger and set it up with a JQL similar as:

Updated <= -5d and Status = Resolved

Meaning the issue is resolved and not updated in 5 days.

unknown

Perfect! That did it! Thanks so much!!

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