Feature #9121

New statuses not available for use

Added by Yehuda Katz over 9 years ago. Updated over 9 years ago.

Status:NewStart date:2011-08-25
Priority:NormalDue date:
Assignee:-% Done:


Category:Issues workflow
Target version:-


This issue is mentioned in the FAQ along with the way to fix it.
The trouble is: We have 7 roles, 6 trackers and 9 statuses and updating each one when we added each new status was a major pain. We are talking about adding another status, but we are not doing it because the process to have it work is too long and complicated.

After all that background: the feature we would like to see is some way to easily add a new issue status to all roles at once. We can go back later and remove it from the ones who should not have it.

About your application's environment
Ruby version              1.8.7 (i386-mingw32)
RubyGems version          1.7.2
Rack version              1.1.2
Rails version             2.3.11
Active Record version     2.3.11
Active Resource version   2.3.11
Action Mailer version     2.3.11
Active Support version    2.3.11
Edge Rails revision       unknown
Application root          c:/Web/redmine
Environment               production
Database adapter          mysql
Database schema version   20110511000000

About your Redmine plugins
Redmine Doodles plugin             0.5.1
Redmine Light Box plugin           0.0.1
Redmine Attach Screenshot plugin   0.0.4
Redmine ChangeAuthor plugin        0.0.2
CAS Authentication                 0.0.3
Redmine Whining plugin             0.0.4
Redmine Time Tracker plugin        0.4

Related issues

Duplicated by Redmine - Feature #9226: Add new issue status to all workflows by default New 2011-09-11


#1 Updated by Jean-Baptiste Barth over 9 years ago

My personal opinion is: "if it's too long and complicated, then you probably don't really need this new issue status".

Anyway, if you want such a feature to be included in a future release, you could help us specify how it could work, it would save developers a lot of time: think about what it could be, what links or buttons or options we should have, how it should behave in standard cases, edge cases, etc. If you have some ideas about the design, build a mock (balsamiq is perfect for that for instance).

#2 Updated by Yehuda Katz over 9 years ago

I can't comment on the number of issue statuses other than to say it is sometimes best to let management do what they want.
I will see if I can mock up something in the next few days.

#3 Updated by Etienne Massip over 9 years ago

See #9226 for patch.

#4 Updated by Yehuda Katz over 9 years ago

I will try out that patch...

#5 Updated by Jan from Planio www.plan.io over 9 years ago

Looking forward to your feedback.

#6 Updated by Yehuda Katz over 9 years ago

The patch works for me.
My only comment is that it appears that the built-in workflows leave the diagonal line of status->itself unchecked. Not sure if that really matters.

#7 Updated by Jan from Planio www.plan.io over 9 years ago

Somebody please close this issue. Discussion and patch solving it are in #9226

#8 Updated by Etienne Massip over 9 years ago

Actually we use to close duplicates, not duplicated, that's why I let it open.
And I don't close duplicate #9226 because of the patch.

#9 Updated by Jan from Planio www.plan.io over 9 years ago

okay - sorry about that. I'll keep it in mind for next time.

Also available in: Atom PDF