Sidehistorik
...
Keep Your workflows relative simple, and break them into sub-workflow handled by subtasks or links if possible. This has several advantages:
...
C. Parallel processing can be done on subtasks sub- or linked tasks by several other Assignee's - whereas one large workflow is seriual on serial with one Assignee at the time.
...
Also, take a loose perspective on restrictions and conditions, setting the workflow up with tight restiction restrictions breaks agility in the real world, for example under ilness illness and leave, issues can be stuck.
...
| Tip |
|---|
A. Assigning the Issue to another user (e.g. getting it done/out of sight) B. Sharing the Issue with another user (can be making a subtask for fullfilmentfullfillment) C. Money (Bonus) D. Serious goodwill |
...
Most of the time, "A" is the common (and powerfullpowerful) reason that drives the normal JIRA user.
...
I have seen this all the time in reallife real-life systems:
| Advarsel |
|---|
Users does not transist Issue unless one of the reasons above is the motivator for making the transition. |
...
A. Only to make steps that fullfills fulfills the drives/motivators mentioned above in the box.
...
Is dont say, "dont use" - but "use with caution and keep everyting everything updated".
If You are using plugins and custom code, do keep an eye on the catalina.out and atlassian-jira.log for stuff as:
...