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 to Closed?

Darryl St_ Pierre

Legacy Automations used to include a rule to transition Resolved items to Closed after a designated period. I believe our older JSM projects had this enabled by default.

We recently created multiple new service projects and discovered that this automation no longer exists.

Does anyone know why this is no longer included (assuming it previously was and that it's not something I inherited from a previous admin)? Current workflows still include the transitions from Resolved and Canceled to Closed. Why wouldn't we want to 'close the loop' automatically?

Accepted answers

Fernando Eugênio da Silva

@Darryl St_ Pierre ,

Legacy automation is being superseded by automation. The automation rules enabled by default for JSM projects are beeing designed in 'Templates' section on your Automation resource.

For example: For the Automation rule that sent issues for 'Closed' due inactivity you can use the template "Resolve issues due to inactivity".

Go to Automation > Select "Templates" > Select the rule > Change the values inside the rule.

For JQL change status from 'In progress' to 'Done', change the days for inactivity also and for action 'Transition issue', change the status to Closed.

You will have the same rule that Legacy Automation offers, but now included on the correct Automation resource.

Regards,

Fernando

All comments

Dan Breyen

Hi Darryl, I used a variant of this solution to do the same thing: Auto Close

Every morning at 9AM, I look for issues that have been resolved for 5 days and then close them. You can still have it do the comment or not. Mine doesn't.

I could be wrong, but I don't remember seeing that exact automation back in January, but I saw this and figured I could tweak it.

Hope that helps.

Fernando Eugênio da Silva

@Darryl St_ Pierre ,

Legacy automation is being superseded by automation. The automation rules enabled by default for JSM projects are beeing designed in 'Templates' section on your Automation resource.

For example: For the Automation rule that sent issues for 'Closed' due inactivity you can use the template "Resolve issues due to inactivity".

Go to Automation > Select "Templates" > Select the rule > Change the values inside the rule.

For JQL change status from 'In progress' to 'Done', change the days for inactivity also and for action 'Transition issue', change the status to Closed.

You will have the same rule that Legacy Automation offers, but now included on the correct Automation resource.

Regards,

Fernando

Darryl St_ Pierre

Thanks Fernando. I am aware that Legacy Automation is deprecated and did see the Inactivity rule that you pointed out. I skipped past it as it seemed more specific than what I wanted, but I will use a modified version to accomplish my goal.

I am still curious if there is any logic in not automatically setting an issue to Closed once it's Resolved, Done, Canceled for a period of time.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management