The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automatic closure of issues

Melle van Keulen
Contributor
July 8, 2021

I'm trying an automation that automatically closes issues if it's in a certain state (open) and hasn't been updated for a certain number of days (14d).

 

When I run the automation, I get an error which says: "The automation rule "...automation rule..." failed due to an error in your Jira installation.

Can anyone tell me what is wrong with this installation? 

 

Automatic closure of issues.PNG

2 answers

2 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Joseph Chung Yin
Community Champion
July 8, 2021

@Melle van Keulen -

In addition to what @Jack Brickey has mentioned, you should also look to see if your project's WF allows a transition from the OPEN status to be moved into the CLOSED status.  If not, then you must create that transition.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Melle van Keulen
Contributor
July 11, 2021

Both @Jack Brickey & @Joseph Chung Yin , thank you! The workflow didn't allow a transition from open to closed, I think that was the cause. 

0 votes
Answer accepted
Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 8, 2021

The error doesn’t seem to be automation rule specific. Can you write any other basic rules and get it to succeed? Just try to create a manual rule that creates an issue. If you continue to get that error I would contact Atlassian support directly.

TAGS
AUG Leaders

Atlassian Community Events