|
[
Permlink
| « Hide
]
Owen Fellows added a comment - 10/Nov/03 01:16 AM
We plan to implement editable work flows and also multiple work flows in the Enterprise edition. I'm not sure if we are going to do Issue Type works flows but we will consider during design and implementation.
We are looking at buying JIRA Enterprise as a potential replacement for a couple of different systems used by different groups in my organization (e.g. Development, Help Desk, Client Support). Having the ability to define different workflows for different projects would be a huge plus.
This feature is required for big organizations even at the issue type level.
The workflow web editor will be usefull only if we can define different workflows per project.
Once the workflow is configurable another step can be added to the workflow - approve issues - which can be only given to the reporter.
When the repoter is made editable, it would be possible to raise the issue on behalf of an external user and hence let them (and only them) "approve" the issue before it is closed. From reading these notes and notes on the linked issues I cannot determine the proposed functionality of per project workflow in release 2.7 ent.
My biggest question is if it will be possible to adjust workflow by issue type, and if not how difficult it would be to extend the code to do so. William,
Workflow in 2.7 Enterprise will be configurable per issue type per project (or just per project is such granularity is unnecessary). Issue type granularity is as necessary as project type granularity.
A request for a new feature is not managed the same way as a bug report is. right right, what is needed by you may or may not be needed by others. The point is that either will be supported. Or, rather, (as I understand it) if you elect to have workflow differ by project you'll be able to have it differ by issue type as well. So if you have 3 different workflows I can envision a setup like this:
project 1 If that's what will be possible then it'll be flexible enough for my groups. Not to confuse the issue, but I just ran across
William,
Yes, 2.7 Enterprise workflow will be that flexible. I'll comment on Updated the fix for version to be Enterprise. Apologies for the confusion.
Linking this Issue as we should consider how are notifications and statistics are going to be handled when we can configure workflows.
It will probably also be necessary to be able to configure what issue status JIRA considers as "open". See JRA-3949.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Closed
Major
Ability to configure the workflow by project or issue type
