Feature #11313

Automatic closing of resolved issues

Added by Pavel Loginov about 5 years ago. Updated 13 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues workflow
Target version:Candidate for next major release
Resolution:

Description

Are there any plans to implement this feature?
Would be great to turn on automatic closing of issues, if they have been marked as resolved for X days.
I know, that there is a plugin there, but it's not been updated for quite a while now and doesn't install on some instances of RedMine.
What do you think guys?


Related issues

Related to Redmine - Feature #1306: resolution fixed and % done out of sync New 2008-05-26
Duplicated by Redmine - Feature #16769: auto-close resolved issues Closed

History

#1 Updated by Alex Shulgin about 5 years ago

What is the point? Any resolved issue is also considered closed (by default.)

#2 Updated by rm user about 5 years ago

Yes, it would be helpful.

1) Resolved doesn't mean issue is closed
2) Closed issue means you don't need to get back to issue anymore, it's completely closed.
3) Resolved doesn't mean always that issue was properly fixed, very often it needs testing.

#3 Updated by Pavel Loginov about 5 years ago

Exactly. In our workflow every resolved issue needs to be closed by project leader or issue author. However, people are no robots and sometimes miss/forget to review a resolved issue which then simply goes down the issue queue. Would be highly useful if such issues could be auto-closed after "expiration".
So I think it's pretty simple and straight forward: if an issue's status was "A" for X days, then it's status is changed to "B". That's it.
Is it possible to just update the old plugin https://github.com/edtsech/redmine_x_closed/tree so that it installs on the newest versions of Redmine?

Here's another request for this, posted a year ago: http://www.redmine.org/boards/3/topics/20046 ...

#4 Updated by Alexey Chepurnykh over 4 years ago

It's a highly required feature. In our installation we have an agreement: if a resolved issue is not closed for 30 days, we close it by hands. The "Langoliers" eat my time. Please, help.

#5 Updated by Filou Centrinov over 4 years ago

For "Resolution: Cant reproduce" this feature would be also helpful. A suitable delay time might be 90 days.

#6 Updated by Dipan Mehta over 4 years ago

There is some interesting discussion on #1306 for similar aspect.

#7 Updated by Anonymous over 4 years ago

For me it would also be useful to have such a feature. For me, the inspiration is the (old / classic-style) SourceForge.net tracker. There, a status "Pending" exists for issues. If an issue is put into status "Pending", then if no change is made to it within 14 days, it is automatically closed. On the other hand, if a change is made, it is automatically put back to status "Open".

Having such a feature would be highly useful to us. And perhaps also to redmine.org: There are many ancients reports here, and for many, redmine staff now is adding comments like "Please respond until DATE, otherwise we will close this issue". But staff has to remember those issues, and on/after DATE, go back to them, and change their status manually to closed. With a "pending" status that could be automated.

Of course in Redmine, one may want to have a somewhat more general "status transition" facility. I.e. it would be nice if each issue status would get these extra fields (in addition to the existing "Name", "Issue closed" and "Default value"): * "If issue is in this status for more than [ checkbox / textfield ] days, change status to [ popup ]." * "If issue is updated while in this status, change status to [ popup ]."

(Of course the last option would only have an effect if the user making the issue update did not select some other target status manually).

#8 Updated by Evgeny Smirnov over 4 years ago

+1

#9 Updated by Miodrag Milic almost 4 years ago

+1

#10 Updated by Matthew Houston over 3 years ago

This would also be helpful in our environment.

Just as an example, in our internal helpdesk system when a ticket is solved it will go into a 'Solved / Resolved' status, then if no feedback is provided by the tech or user it is automatically closed after 2 days. This allows the users a testing time while not clogging up the tech's ticket lists with active tickets. (The 2 days is adjustable, just what works for us).

#11 Updated by Philippe Lafoucrière over 3 years ago

+1
Our clients don't always close resolved issues :(

#12 Updated by Daniel Felix over 3 years ago

Yes, we encounter sometimes the same issues. Some issues have a long wait time until they were really closed.

#13 Updated by Jonas Nielsen over 3 years ago

+1

#14 Updated by Willian Dolence Ribeiro over 3 years ago

+1 here!

#15 Updated by Adnan Topçu over 3 years ago

+1
Nobody does not close the resolved issue.

#16 Updated by Alfredo Mezquita over 3 years ago

Pavel Loginov wrote:

Exactly. In our workflow every resolved issue needs to be closed by project leader or issue author. However, people are no robots and sometimes miss/forget to review a resolved issue which then simply goes down the issue queue. Would be highly useful if such issues could be auto-closed after "expiration".
So I think it's pretty simple and straight forward: if an issue's status was "A" for X days, then it's status is changed to "B". That's it.
Is it possible to just update the old plugin https://github.com/edtsech/redmine_x_closed/tree so that it installs on the newest versions of Redmine?

+1!

Totally agree with you. This feature would be very useful for our company as well. When a issue has been resolved, we notified it to the client and if everything is ok or if we don't receive any answer in 3 days, we close the issue manually. A feature like this could automate this process and it would be very useful for us.

Is there any chance to include this feature into the roadmap for the next product iterations?

#17 Updated by Toshi MARUYAMA over 3 years ago

#18 Updated by Artyom Tuprikov about 3 years ago

+1
Highly requested!

#19 Updated by Josep Mª Mas about 3 years ago

+1
Would be great!

#20 Updated by Luis Blasco about 3 years ago

+1
Thanks in advance!

#21 Updated by Cristiano Cesario almost 3 years ago

+1
Thanks!

#22 Updated by Dmitry Lukashin almost 3 years ago

+1 vote

#23 Updated by Stephan Smola over 2 years ago

+1
This is essential if you want to have a retest for a resolved issue.

#24 Updated by Jogi 1j over 2 years ago

I tried to create a plugin for this problem, but it's my first plugin, so I'm not sure if you find an error, please contact me, thank you. It's not the final version.

http://www.redmine.org/plugins/redmine_closes_resolved_issues

#25 Updated by David BOUCHE over 2 years ago

+1
Highly requested!

Jogi : your plugin is not compatible with 3.0 redmine installation.

#26 Updated by Ivan Prokudin about 2 years ago

I've tried Jogi's plugin and and it's suit me (I use redmine 2.6). The only thing that I need is notifications about closing the issues. So I'm offering USD 20.00000000 via FreedomSponsors to the first person who fix it.

Offer link: https://freedomsponsors.org/issue/732/close-notifications

You can also join me and throw in a few bucks there and we'll get it fixed faster :)

If you fix this issue (see my acceptance criteria there) please use that site to request your payment.

#27 Updated by Pongtawat C almost 2 years ago

Ivan Prokudin: Maybe this is something you want?

https://github.com/jkraemer/redmine_issue_reminder

#28 Updated by Etienne Massip almost 2 years ago

  • Target version set to Candidate for next major release

#29 Updated by Loïc Barreau about 1 year ago

+1 : will be very usefull for us to.

#30 Updated by JW Fuchs about 1 year ago

+1

#31 Updated by Mathieu Simard 13 days ago

+1

Also available in: Atom PDF