https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292010-04-27T16:50:20ZRedmineRedmine - Feature #4828: Dynamic / modular workflows.https://www.redmine.org/issues/4828?journal_id=161912010-04-27T16:50:20ZDaniel Miller
<ul></ul>This feature-request appears to be in actuality multiple feature-requests (that perhaps should be tracked separately). For example,
<ol>
<li>One feature could be a static (for all issues) modular work-flow.</li>
<li>Another feature could be to choose one of several predefined static work-flows on a per-issue basis.</li>
<li>Yet another separate feature could be to extend these 2 concepts on a per-issue basis, where a base work-flow can be adjusted (additions or subtractions) per issue by a privileged role.</li>
</ol>
<p>That third one could get rather complicated due to, in its most extreme form, an editor of an arbitrarily-complex graph or state-machine or petri net on a per-issue basis.</p>
<p>I do agree with the overall sentiment that the mental model currently in place in Redmine's work-flows is too simplistic to compete with DevTrack's rich work-flow feature-set.</p> Redmine - Feature #4828: Dynamic / modular workflows.https://www.redmine.org/issues/4828?journal_id=161992010-04-27T17:34:09ZDaniel Miller
<ul></ul><p>The multiple static work-flows in this feature-request might be a duplicate of feature-request <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Assign different status sets and workflows for separate projects (New)" href="https://www.redmine.org/issues/973">#973</a>.</p> Redmine - Feature #4828: Dynamic / modular workflows.https://www.redmine.org/issues/4828?journal_id=268652011-03-23T10:23:37ZToshi MARUYAMA
<ul><li><strong>Category</strong> set to <i>Issues workflow</i></li></ul>