Project

General

Profile

Actions

Feature #973

open

Assign different status sets and workflows for separate projects

Added by Clyde Goffe about 16 years ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues workflow
Target version:
-
Start date:
2008-04-02
Due date:
% Done:

0%

Estimated time:
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

Related to Redmine - Feature #1853: Make Projects truly independent of each otherNew2008-09-04

Actions
Related to Redmine - Feature #3726: Trackers per RoleClosed2009-08-10

Actions
Related to Redmine - Feature #2905: Enable per-tracker issue status setClosed2009-03-05

Actions
Related to Redmine - Feature #1966: Different set of Issue Statuses per TrackerClosed2008-09-29

Actions
Related to Redmine - Feature #2240: Ability to constrain tracker by roleClosed2008-11-27

Actions
Related to Redmine - Feature #285: Tracker role-based permissioningClosedJean-Philippe Lang

Actions
Related to Redmine - Feature #4828: Dynamic / modular workflows.New2010-02-13

Actions
Related to Redmine - Feature #10331: Per-project 'Issue Closed' status customizationNew

Actions
Related to Redmine - Feature #7839: Limit trackers for new issue to certain rolesClosedJean-Philippe Lang2011-03-11

Actions
Related to Redmine - Feature #5991: Tracker should have it's own default issue statusClosedJean-Philippe Lang2010-07-29

Actions
Has duplicate Redmine - Feature #6436: Ticket Workflows as independent entities.Closed2010-09-20

Actions
Has duplicate Redmine - Feature #10039: Issue statuses for each projectClosed

Actions
Actions #1

Updated by Clyde Goffe almost 16 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.

Actions #2

Updated by Mischa The Evil over 15 years ago

+1 :)

Actions #3

Updated by Thomas Pihl over 15 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

Actions #4

Updated by Eric Davis over 15 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.

Actions #5

Updated by Clyde Goffe over 15 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.

Actions #6

Updated by Jim Jones over 15 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.

Actions #7

Updated by Brock Gunter-Smith over 15 years ago

+1
Redmine should ideally allow setting master workflows and then override them at the project level if required.

Actions #8

Updated by Harry Yamamoto over 15 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...

Actions #9

Updated by Stephanie Collett over 15 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.

Actions #10

Updated by Enderson Maia about 15 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.

Actions #11

Updated by Haomin Liu about 15 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.

Actions #12

Updated by Krzysztof Szalast about 14 years ago

+1
I also need that feature

Actions #13

Updated by Alexander Usikov about 14 years ago

+100
Actually we can't use redmine because of lack of this feature

Actions #14

Updated by Nikolay Kotlyarov about 14 years ago

+1

Actions #15

Updated by Raphael B almost 14 years ago

+1

Actions #16

Updated by yannick quenec'hdu almost 14 years ago

+1

Actions #17

Updated by Brent Shaffer over 13 years ago

+1. This would be such an amazing feature.

Actions #18

Updated by goldleaf asd over 13 years ago

SPAM

Actions #19

Updated by goldleaf asd over 13 years ago

SPAM

Actions #20

Updated by Ryan Cross about 13 years ago

+1

Actions #21

Updated by Etienne Massip about 13 years ago

  • Category set to Issues workflow
Actions #22

Updated by ee se about 13 years ago

+1

Actions #23

Updated by Overmind Eternal Will about 12 years ago

+1
Also for my company this feature is blocking the adoption of Redmine for our workflow. :(

Actions #24

Updated by Patrick Feistel over 11 years ago

+1

Actions #25

Updated by Kenichi Handa over 11 years ago

+1

Actions #26

Updated by Daniel Felix over 11 years ago

Hi there,

I think this would be a great feature!

Some suggestion would be to remove the workflow and ticket status menulinks from the administration panel or define them new.
The new implementation could be something like this:
  1. Per project settings, each projectmanager can define trackers with a workflow set for this project. They can also add trackers, which already exists (to prevent hundreds of "bug"-trackers) and redefine a workflow for their project. The workflow always will be blank or get some default values if a projectmanager adds an existing tracker to his project. This prevents some information disclosure.
  2. Current existing trackers and their workflows will be reassigned to the existing projects and can be redefined after upgrade
  3. If a project is going to be deleted, their will be a check if the used tracker is reused in some other project. Otherwise it will be dropped with the project too.
  4. Workflow sets will always be dropped if a project is deleted
  5. Tracker and workflow creation would be managed with some permissions (this way old-fashioned administrator can restrict this and manage the trackers in the old way).
  6. The projectsettings (in administration) will get a new checkbox (flag), "Use own workflows". This flag defines if the projects allow own workflow and own tracker creation, if this flag isn't defined, the project will use the systemwide workflows with the trackers, which are assigned by the projectmanager.

This will help administrators, and give them the abbility to outsource some management to the corresponding projectmanager.

What do you think?

Actions #27

Updated by Daniel Hochman over 10 years ago

Not sure if this workaround was mentioned before, but you can create new roles for this purpose. For example, I have Role # 1 which I associate with specific statuses and workflow and only use Role # 1 in Project # 1. Then I have Role # 2 which I associate with other statuses and workflow and only use Role # 2 in Project # 2.

Not the cleanest but I think it works.

I also should mention that Admins will see all statuses regardless of roles.

Actions #28

Updated by Lubos Racansky over 10 years ago

+1

Actions #29

Updated by Toshi MARUYAMA over 10 years ago

  • Related to Feature #7839: Limit trackers for new issue to certain roles added
Actions #30

Updated by Domingo Galdos about 10 years ago

+1

We could really use this. Our redmine instance is used by multiple stakeholders who want their own workflows, but as is they cannot manage them themselves, but must request it from the central administrator of the redmine instance, and even then care must be taken to avoid/resolve conflict.

Actions #31

Updated by Toshi MARUYAMA about 10 years ago

  • Related to Feature #5991: Tracker should have it's own default issue status added
Actions #32

Updated by Sergey Semenov almost 9 years ago

+1 it is highly desirable feature for multy-project deployments.

Actions #33

Updated by Vlad Vor almost 9 years ago

+1 I need it every day!!!
Going to try this plugin https://github.com/jjrosalesuci/redmine_auto_assigned

Actions #34

Updated by Leonid Byakov over 8 years ago

+100 Really!

Actions #35

Updated by Joaz Soares over 8 years ago

+1

Actions #36

Updated by Dmitry Ro over 8 years ago

+1

Actions #37

Updated by Kirill Prokin over 8 years ago

+1

Actions #38

Updated by budo kaiman over 8 years ago

+1

Actions #39

Updated by Alexander Lapshin over 8 years ago

+1

Actions #40

Updated by Inese Ez over 8 years ago

+1

Actions #41

Updated by Gayathri Jayakumar about 8 years ago

+1 I would also require this kind of feature where workflow can be defined at a project level. Since we have project that follow different workflows and statuses

Actions #42

Updated by Anh Le Giang over 7 years ago

+ 1
I need different issue status for different project since we also have marketing and sales team using Redmine.

Actions #43

Updated by Go MAEDA over 7 years ago

Actions #44

Updated by ale dp over 7 years ago

+1

Actions #45

Updated by Stephane Evr about 7 years ago

+1

Actions #46

Updated by Frederico Camara about 7 years ago

Maybe this is related to Feature #20384, which I implemented at work. We have been using it for about a year:

I added an abstraction layer called Workspace so you could have different workflows. You then choose which workspace each project is using.

I added a patch there against Redmine 3.3-stable. It can potentially break some plugins, I have some fixed at github.com/fredsdc.

Actions #47

Updated by Axel Ronsin almost 6 years ago

+1

Any chance this will ever happen ?

Actions #48

Updated by sebastien lemaitre almost 6 years ago

+1

Actions #49

Updated by Bartlomiej Skwira almost 5 years ago

11 years later and this feature is still more than welcome. Any chance to actually have it implemented?

Actions #50

Updated by Luis Blasco over 4 years ago

+1

Actions #51

Updated by Elymar Silva about 4 years ago

+1

Actions #52

Updated by Gianni Cavallotto over 3 years ago

+1
At least as a first feature it would be enough to select which statuses can be visible or not by projects.
The administrator would have to take care on his/her own to maintain workflows feasible at any time a project define its set of statuses and not all combinations of hide and show might be possible. But at least...

Actions #53

Updated by Jihyeon Gim almost 3 years ago

+1

Actions #54

Updated by thuruk thuruk over 1 year ago

+1

I think it is a real weakness for redmine to not have workflows by project. This was also raised up but shot down in #35544.

Taking my own example here, I've got 2 trackers, Bug and Feature.
However I have a project where issues need 2 levels of approval, as well as other checks.
On the other hand, I have a project for an internal ERP where the workflow is basically just New -> In progress -> Done.

The solution here is clearly not to create 2 different trackers, that would mean that expanding on this principle would lead to having trackers specific to each project's needs.
The simplest solution as it stands would be to create specific roles per project instead of specific trackers. But we're still duplicating something per project, so this is not a good solution.

I truly think this is preventing a lot of the potential use of Redmine at scale.

Thanks :)

Actions #55

Updated by Jet Yan 3 months ago

+1

Actions

Also available in: Atom PDF