How to add Post Functions on a Simplified Workflow to set new assignee based on the current status?

[Agilan Ampigaipathar]

I'm trying to set three statuses or transitions where from TO-DO, it would go to "primary" and on this status/transition, a new assignee would be given. Once, this assignee is done, they would pass it on to the "secondary" status/transition under a new assignee. Should I go about making three statuses or transitions? My Jira administrator recently told me that the users are only limited to the "Simplified Workflow", and as seen by the screenshot, the post function is unclickable. Is there a different way to access the post functions and/or achieve the strategy I'm trying to implement? 

[Blazej Borucki]

Hi Agilan, 

you need one transition with post function.

To add post function go to Settings > Workflows > your workflow > edit > view as a diagram > select the transition > click post functions > add and select proper option (first ones) or Update issue filed > site field = assignee and select fixed approver. 

In case you would like to put more conditions in the post function I suggest Automation or Scriptrunner apps. 

[Agilan Ampigaipathar]

Hi Blazej, 

Thanks for the reply, is there a way to access the post function in the Simplified Workflow or an alternative way to do it without going through post functions? The post function as shown in the screenshot is unclickable. I tried getting the Scriptunnner app, but my team is limited to Automation Lite and so I can't get Scriptrunner unfortunately.   

[Blazej Borucki]

Not sure why... can you access it in draft workflow?

[Agilan Ampigaipathar]

I can add/edit statuses and transitions, but it doesn't seem to let me access post functions here. This is what I see when I try to edit the transition, and Learn More under the "Post Functions (5)" takes me to this documentation: https://confluence.atlassian.com/display/JIRASOFTWARESERVER0712/Advanced+workflow+configuration

[Andrew Laden]

Are you a full jira administrator or just a project administrator.

Project administrators are limited to a small set of administrative functions that they can do. Anything beyond that would require full jira administrative rights.

It looks like you are falling into that category. You would need to be a full jira admin to be able to modify conditions/validators/workflows.

https://confluence.atlassian.com/adminjiraserver0713/managing-project-permissions-964983417.html

Gives the project administrator the ability to edit workflows and screens under certain conditions.

Collapse

• The workflow must not be shared with any other projects, or be a system workflow.
• To add a status, the status must already exist in the Jira instance i.e. the project admin can't create new statuses or edit existing statuses.
• To delete a status, the status must not be used by any of the project's issues.
• The project admin can create, update or delete transitions, but they can't select or update a screen used by the transition, or edit or view a transition's properties, conditions, validators or post-functions.

Collapse

• The screen must not be a default system screen.
• The screen must not be shared with any other projects, or used as a transition screen in workflows.
• The project admin can add, remove and rearrange system fields.
• The project admin can add, remove and rearrange existing custom fields, but they cannot create custom fields.

[Agilan Ampigaipathar]

Hi Andrew,

Thanks, it turns out I am just a project administrator, but not a full Jira administrator. The DevOps team said end-users like me are only.supported with the Simplified Workflow for now, but will later on be able to get these settings in the future state.

Thanks again for all the help guys, I'll try to implement the post functions and/or Scriptrunner when we get the chance!