Article aims to explain how to remove "Send to Supervisor" step from Vacation Manager workflow in a safest manner possible.
Instructions
1) Login as Jira administrator and as presented below go to "Issues" (1), then "Workflows" (2). Scroll down to find "VACMAN Vacation Manager Workflow" (3) and press "Copy" (4):
Do not alter anything on the original "VACMAN Vacation Manager Workflow" - it can make Vacation manager unusable.
2) Name copied workflow as you wish:
3) Now it's time to edit copied workflow. Make sure after edition of a Vacation Manger workflow's copy, created vacation request goes directly to "Waiting for approval" status. After you finish with edition, it should resemble the one presented below:
I've marked transition "Delete" and status "Created" that needs to be removed and how "create" transition should be linked now with "Waiting for approval" (to get a workflow like the one presented above):
Please refrain from removing any status and transition that leads to supervisor acceptance of a leave - if supervisor's role is to be omitted, then user's remaining quota of available days for particular leave won't be calculated properly. If you plan to make a workflow looking like a one below - be advised - it won't work:
4) Post-function of "create" transition needs to be altered:
Please edit the post-function marked in red:
to this setting:
when it's changed to not forget to press "Publish" button:
You need to repeat those steps for post-functions of other transitions, to make sure there's a correct allocation of assignee to the issue (i.e. transition "approve" should automatically reassign the issue back to a requesting user via the use of post-function as well).
5) Remember about saving workflow changes and next step is to assign Vacation Manager issue types (if you have already created it) to a workflow copy:
If there are no Vacation Types created yet, then this step is to be skipped.
6) Finally you can request a leave that goes directly to user's line manager directly after pressing "Create":
Manager sees it like that:
and decided to approve it - issue gets reassigned back to the reporting user:
