
|
If you were logged in you would be able to see more operations.
|
|
|
JIRA
Created: 11/Jan/05 01:03 PM
Updated: 04/Apr/07 12:04 PM
|
|
| Component/s: |
Workflow
|
| Affects Version/s: |
3.0.3 Enterprise
|
| Fix Version/s: |
None
|
|
|
Issue Links:
|
Reference
|
|
This issue relates to:
|
|
|
JRA-5386 Activating workflows in JIRA Enterprise is unintuitive
|
|
|
|
|
|
This issue is related to:
|
|
JRA-7661
Ability to Edit Active Workflow - Editing Workflows is too inflexible
|
|
|
|
|
|
|
|
Think about this scenario; Before entering production with a cusom workflow, you develop it and test it on an offline system. This system only hava a minimal number of users and issues. When you develop a workflow you might have to write a custom plugin. This plugin must be tested several times inside Jira. This whole process requires a lot of changes and tweaks to the workflow all the time. And this means you have to copy active workflow, remove workflow scheme from project, remove workflow from scheme, assign workflow to scheme, add workflow to project every time you want to test a new change. Please let us have an development mode for workflows, making them easier and faster to develop!
|
|
Description
|
Think about this scenario; Before entering production with a cusom workflow, you develop it and test it on an offline system. This system only hava a minimal number of users and issues. When you develop a workflow you might have to write a custom plugin. This plugin must be tested several times inside Jira. This whole process requires a lot of changes and tweaks to the workflow all the time. And this means you have to copy active workflow, remove workflow scheme from project, remove workflow from scheme, assign workflow to scheme, add workflow to project every time you want to test a new change. Please let us have an development mode for workflows, making them easier and faster to develop! |
Show » |
|
Well, you can just have two workflow schemes + workflows in the system,
and then just switch the scheme associated with the project to test
changes, which isn't too painful, is it?
Cheers,
Jeff