Feature #973
Assign different status sets and workflows for separate projects
| Status: | New | Start date: | 2008-04-02 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Issues workflow | |||
| Target version: | - | |||
| Resolution: |
Description
Hey,
Currently it seems the statuses and workflows are system wide settings.
It would be good to have the flexibility to create multiple status sets along with their accompanying workflows. Then assign a set of statuses+workflows to their respective projects. This can be in addition to an already defined system wide setting that can be overridden if necessary.
This is in the event a team working on a particular project has statuses and workflow needs that are different from the rest of the organization or team members of other projects.
I haven't seen a way to accomplish this in the current version. If its already available can someone please tell me how to do so.
Thanks,
Clyde
Related issues
History
#1 Updated by Clyde Goffe about 4 years ago
Is it possible to plan this for version 0.8? Is it even feasible at this point? Is it too much of an architecture change?
The lack of this feature is the only thing that's preventing my company from taking a serious look at Redmine.
#2 Updated by Mischa The Evil almost 4 years ago
+1 :)
#3 Updated by Thomas Pihl almost 4 years ago
I use a very crude homemade "fix/patch" to work around this. I create different statuses and workflows per project/tracker. It ruins some of the nice summary features with some 90 different statuses (eventually i might be able to filter that as well).
I prefix workflow-name and status-name with some identifier. I have added a filter-field when creating/editing workflows to avoid the huge matrix otherwise loaded/viewed.
I would prefer not to show my changes since i'm still a novice in rails and my patches are all but rubyish (but i am learning). Default status has another crude fix needed so that users start with a status valid for that workflow.
It's dirty but working for my users at this point in time.I REALLY vote +1 for a good solution to this feature.
/T
#4 Updated by Eric Davis almost 4 years ago
Thomas Pihl wrote:
I would prefer not to show my changes since i'm still a novice in rails and my patches are all but rubyish (but i am learning). Default status has another crude fix needed so that users start with a status valid for that workflow.
It's dirty but working for my users at this point in time.I REALLY vote +1 for a good solution to this feature.
Go ahead and post your patch. It might help someone else and others could improve on it to make it more rubyish.
#5 Updated by Clyde Goffe almost 4 years ago
I agree with Eric. Please post your patch. Hopefully it will be improved upon and will become an official patch and slated for a future release.
#6 Updated by Jim Jones almost 4 years ago
+1 for this feature.
We are in the same situation. We'd love to manage all our projects with redmine but many projects have drastically different workflows.
For now we've settled on using redmine for the programming stuff and another tool for the rest - but obviously that's a less than ideal solution.
#7 Updated by Brock Gunter-Smith over 3 years ago
+1
Redmine should ideally allow setting master workflows and then override them at the project level if required.
#8 Updated by Harry Yamamoto over 3 years ago
Thomas Pihl wrote:
I use a very crude homemade "fix/patch" to work around this. I create different statuses and workflows per project/tracker. It ruins some of the nice summary features with some 90 different statuses (eventually i might be able to filter that as well).
I prefix workflow-name and status-name with some identifier. I have added a filter-field when creating/editing workflows to avoid the huge matrix otherwise loaded/viewed.
I would prefer not to show my changes since i'm still a novice in rails and my patches are all but rubyish (but i am learning). Default status has another crude fix needed so that users start with a status valid for that workflow.
It's dirty but working for my users at this point in time.I REALLY vote +1 for a good solution to this feature.
/T
Yes,like workflow-name and status-name for grouping the workflows and statuses...
Hope the patch...
#9 Updated by Stephanie Collett over 3 years ago
+1 We would heavily use this feature if available. Right now our PMs have to settle on one standard, but they frequently ask for more flexibility.
#10 Updated by Enderson Maia about 3 years ago
+1
Thomas Pihl wrote:
I would prefer not to show my changes since i'm still a novice in rails and my patches are all but rubyish (but i am learning). Default status has another crude fix needed so that users start with a status valid for that workflow.
Make your patch public, so others can contribute.
This feature wuold be great for me, co I can use Redmine for evereyone, and not just the dev crowd.
#11 Updated by Haomin Liu about 3 years ago
+1
I've just proposed a duplicated ticket #2905 for this feature. It would be really nice if we have it in next version.
#12 Updated by Krzysztof Szalast about 2 years ago
+1
I also need that feature
#13 Updated by Alexander Usikov about 2 years ago
+100
Actually we can't use redmine because of lack of this feature
#14 Updated by Nikolay Kotlyarov about 2 years ago
+1
#15 Updated by Raphael B almost 2 years ago
+1
#16 Updated by yannick quenec'hdu almost 2 years ago
+1
#17 Updated by Brent Shaffer almost 2 years ago
+1. This would be such an amazing feature.
#18 Updated by goldleaf asd over 1 year ago
SPAM
#19 Updated by goldleaf asd over 1 year ago
SPAM
#20 Updated by Ryan Cross about 1 year ago
+1
#21 Updated by Etienne Massip about 1 year ago
- Category set to Issues workflow
#22 Updated by ee se about 1 year ago
+1
#23 Updated by Overmind Eternal Will 3 months ago
+1
Also for my company this feature is blocking the adoption of Redmine for our workflow. :(