Feature #559: Workflow Enhancements - Redmine

Feature #559

Workflow Enhancements

Added by Geordee Naliyath over 4 years ago. Updated 4 months ago.

Status:

New

Start date:

Priority:

Normal

Due date:

Assignee:

% Done:

Category:

Issues workflow

Target version:

Unplanned

Resolution:

Description

Here are some suggestions to enhance workflow:
1. Ability to hide unused statuses in workflow definition
At applications level we create many statuses and use only the appropriate ones for creating different workflows. This
creates large number of options when we are at workflow definition screen and it's very difficult to work with or understand
the workflows. We can do either of the following two options to make workflow definitions easier.
a. Use AJAX to hide unused statuses
b. Create ability to add/remove statuses for a particular workflow from the global set

2. Workflow visualization
Once the workflow is defined, if it can be represented in a decision tree either pictorially or using some formatted
table it could be easier to manage. I was thinking of converting organizational processes into Redmine workflow, and
a pictorial representation will appear as the process definition. Conditions for status changes may be missing in this
workflow - that would make it too complicated as well - and that is OK.

wf_visu.JPG (15.7 kB) Keny 31, 2010-10-19 14:17

ro559-add_workflow_graphviz_graph-r4574.patch - Patch against current Redmine Trunk (1.0.5.devel.r4574). (1.1 kB) Mischa The Evil, 2010-12-29 07:01

History

#1 Updated by Nikolay Kotlyarov almost 3 years ago

I think my problem is the same as point 1 above, but supposed solution differs..

The are two problems in our company:(Redmine 8.0)

Project "SomePrj" needs personal workflow "SomePrjWorkflow". Project "AnotherPrj" also needs personal workflow "AnothePrjWorkflow" that resembles "SomePrjWorkflow" but not the same. Project "ThirdPrj" needs a workflow that is completely different from "Some" and "Another". And all of them want to use same statuses for tickets.
But there is only one workflow in Redmine and it affects all projects:(
In project "SomePrj" most of the issues must subordinate "SomePrjWorkflow". They flowing from one person to another and have a number of transitions before it is closed. But there are issues that can be closed in one or two transitions in a vary short period. If those issues would subordinate standard workflow their lifetime would be much greater, for example: issue would wait some person(who is on a vacation) with corresponding role just for " click me forward till SomeStatus ".
Most of the project issues must subordinate "SomePrjWorkflow". But there are "extra" cases when the issue must subordinate its custom workflow. And those cases are not rare in practice.

Workaround:

For custom project "SomePrj" workflow we can create its own special statuses with an unique prefix/postfix: "[SomePrj]New", "[SomePrj]Assigned", "[SomePrj]Closed", etc.
I dunno any:( Because of singular workflow people just do not create such "mini"-issues and try to resolve them by email. That method frequently becomes even more time consuming..

So the requested features are:

Per project workflow
Per issue worklow

Point 2 from Geordee: +1. Some visualization would be great, cause currently it's very easy to get tangled when the statuses number increases.

P.S. Sorry for my English, i know it's bad..

#2 Updated by Michael Ivanov over 2 years ago

#3 Updated by Emil Abdulnasyrov over 2 years ago

#4 Updated by Alexey Skor almost 2 years ago

I'd say +100. this is a killer feature, which would bring Redmine much closer to systems like Atlassian Jira.

#5 Updated by Keny 31 over 1 year ago

File wf_visu.JPG added

Hello,

+1
I'm sharing the workflow definition of more than 10 trackers with other project manager and it is quite difficult and time consuming to maintain a document showing the states and transitions for everybody use.

An automatic generation of workflow visualisation like below will be great:

The color of the arrows represents the autorized transition by profile (manager, developper, customer)

#6 Updated by Dmitry Dusenbaev over 1 year ago

#7 Updated by Ruben Kruiswijk over 1 year ago

#8 Updated by Terence Mill over 1 year ago

Checkout this for "Workflow visualization"

http://www.redmine.org/boards/3/topics/5312

#9 Updated by Mischa The Evil over 1 year ago

File ro559-add_workflow_graphviz_graph-r4574.patch added

And here yet another implementation of a sort of "Workflow visualization" by Ryo SUETSUGU:

Initial blog post:
- http://d.hatena.ne.jp/suer/20100820/redmine_viz
Follow-up blog post:
- http://d.hatena.ne.jp/suer/20100821/workflow_viz_plugin
Quick 'n Dirty plugin introduced in second blog post:
- https://github.com/suer/redmine_workflow_viz

I myself have changed the patches/plugin-source slightly and maintain it as a private patch. I'll attach it to this issue (ro559-add_workflow_graphviz_graph-r4574.patch).

#10 Updated by Terence Mill over 1 year ago

We installed the workflow_graphviz plugin sucessfully on redmine 1.01.

#11 Updated by Toshi MARUYAMA about 1 year ago

Category set to Issues workflow

#12 Updated by Etienne Massip about 1 year ago

Target version set to Unplanned

#13 Updated by Anton Lem about 1 year ago

Workflow visualisation +1

#14 Updated by Terence Mill 10 months ago

THe PLugin seems not to be maintained.
We reported some major bugs , but to response.
https://github.com/suer/redmine_workflow_viz/

#15 Updated by yannick quenec'hdu 4 months ago

Your proposal is interesting. This implies that it is possible to make independent workflow per project, thus also independent issues statues by workflow and for each project.

In view of the evolution of IT projects to Agile methods. Workflow view could be seen with a Kanban view.

A perhaps introduce the notion of limit in the work in progress

Anton Lem wrote: