Move issue automatically from resolved to accepted after 14 days

[Jan Vesely]

Hi,

The questions has been asked years ago and I'm not sure the solution suggested then is still relevant (jelly scripts).

What I'm looking for is this:

1. ISSUE in a project is marked as resolved by developer

2. After a certain period of time, let's say 2 weeks, I want the issue to be moved automatically to ACCEPTED if there was no activity, within the same project

Is there a way to achieve this with JIRA only? Or would I need a plugin for this? OR are Jelly scripts still an option?

Thank you,

Jan

[Alexey Matveev]

Hello,

You would need a plugin for it. Jelly is not used in the newest versions of Jira. 

For example, you could use the Power Scripts plugin.

https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview

You could create a job, which would be executed on schedule. This job would select all issues, which are in the Resolved status for more than 14 days, and this issues would be moved to the Accepted status.

https://confluence.cprime.io/display/SIL/Scheduling+routines

Your script would look like this:

string jql;
jql = "status changed to Resolved before -14d and status = Resolved";
string[] keys = selectIssues(jql);
for(string key in keys) {
  autotransition("Accepted", key);
}

[Romain VELON]

Hello,

This is not possible natively in JIRA

I don't know about jelly script but for sure the plugin "Automation for JIRA" will do it. A very good plugin.

Romain

[Olivia Quakenbush]

Can you explain how to do it in 'Automation for JIRA'?

[Romain VELON]

Hello @Olivia Quakenbush ,

You should be able to set this up with the 'Scheduled' trigger.

The rule would look something like this:

• Scheduled to run once per day with JQL: status = Resolved and updated < -14d
• Transition issue action to move those issues to 'Closed'

The way this works is that the trigger will try to find all issues once per day that are currently 'Resolved' and haven't been updated for longer than 14 days. Only the ones matching this search are then moved to closed.

Romain

[Olivia Quakenbush]

Thank you @Romain VELON, one question, the 'Scheduled' trigger, that is not in 'Automation for Jira', this is just in regular Jira?

[Romain VELON]

No @Olivia Quakenbush , this trigger is part of Automation for JIRA

[Jan Vesely]

Hi all,

Thank you for the great suggestions. AFaik we don't have any of these plugins (yet), I'll take a look at the options you suggested and try to get my organisation purchase one. 

Have a nice day,

Jan

[Payne]

@Nir Haimov mentioned ScriptRunner; we use that one as well for this purpose (escalation), but it offers so much more. It is truly a worthwhile add-on that I highly recommend you look into.

-Payne

[Nir Haimov]

That's right

With scriprunner you can do anything you want in Jira

It's the most valuae plugin in the marketplace.

If you think abkut purchasing something, it should be scriprunner

[Yevgen Lasman]

Why it should be the only option while there are few on the Marketplace?

[Rathna]

Hi @Yevgen Lasman

Just so that you know Script Runner plugin has been around even before any of the current automation plugins did not even existed. I do sincerely appreciate the effort @Jamie Echlin put into this which is and was making every single Atlassian Admin life a lot easier who has more than 3 yrs of exp. Coming back to your question why should someone use only this plugin, Because no other plugin on Marketplace has all (and more) functionality which is equal to this plugin. As @Payne & @Nir Haimov mentioned above.

[Yevgen Lasman]

@Rathna I’m afraid you didn’t get my point at all 🤦🏼‍♂️ But that’s okay, it would be rather an off-topic to the original post. 

[Nir Haimov]

As @Romain VELON said, this is not possible natively in JIRA

If you have Scriptrunner you can do it from there with "Escalation service"

Let us know what you have so we will better help.