Post Function Not Working on Sub-Task Workflow for Assignee

[James Wilhite]

I'm trying to make it so that the assignee doesn't default to the project lead when a sub-task is created.  I read through several different discussions in this forum and decided that the best route would be to create a post function on a separate sub-task workflow to either copy the assignee from the parent, or to make the current user the assignee.  I've tried both of these post functions on the Create transition, and even tried adding in an earlier post-function that clears out the assignee.  However, no matter what I try, the assignee is set to the project lead.  

Can anyone help me figure out what's going wrong?

[John Funk · Accepted solution]

Hi James,

It is not guaranteed that post functions will fire in the order they are listed. I would create a simple Automation for Jira rule to update the Assignee field after the ticket is created.

1. Go to Project Settings > Project Automation (on left-hand menu)
2. Press Create Rule in top-right corner
3. Select the Trigger "Issue Created" and press Save
4. Next Select to add an Action, and choose "Edit Issue"
5. Select the field Label
6. Select the options icon (3-dots) - and choose "Add/remove values"
7. Enter the value you want as a default and press Save
8. Name your Automation and turn it on

Now when each issue is created, it will add the desired default label as long as the issue is created in that project. You might need to refresh the page after each issue creation to see it.

You can do this via global rules to apply to all projects also. You'll need to be a Jira Admin/Site Admin, then instead of going to Project Settings, go to Jira Settings (cog icon on left-hand navigation bar) > System > Automation Rules (left-hand menu).

For more on using Automation For Jira see these help pages.

[James Wilhite]

Thank you, John.  I'd still like to have the Project Lead be the default assignee for all types except for sub-tasks.  I believe that your method would be a global change, right? 

[John Funk]

You can only apply it to certain Issue Types or exclude certain issue types. 

[James Wilhite]

This worked!  But for anyone who finds this in the future, make sure you use the Edit Issue as John mentioned and not the Assign Issue option.  

[John Funk]

Glad it is working for you!

[Daniel McCammon]

I know this is a bit of an older thread, but is there a way to filter for only if the "Automatic" assignee was used on issues creation?

I'm looking to respect the reporter's assignee when defined, but simply change the default assignee when the "automatic" assignee is used.

However, the solution above seems to overwrite the assignee regardless of what was specified. I can filter based on if assignee is EMPTY, but not assignee is Automatic.. 

[John Funk]

Hi Daniel,

Maybe you could put in a condition that checks if the assignee = a particular user

[Daniel McCammon]

Except then we wouldn't be able to manually assign it to them either.. :/

[Amrutanjan Health Care Ltd]

Hi @John Funk ,

It would work with project automation. but what if i want to copy assignee from parent to its sub-task on workflow default post function option, I am not able to do so. I have added "copy field value from other field" post function in workflow post function but its not working.
How can i do that ?

Regards,

Chinmay

[John Funk]

Hi Chinmay,

It is always better to create a new question so more people can help you. When you post to an existing question, on the people on that question will see it. 

I have not tried to do that with a post function. We use JMWE which provides a lot more power for those kinds of things. But I typically use Automation for it. 

[Éric Dumesnil]

I was trying to do the same for the priority -- ended up working for me after I put the copy field post-function step before the "Creates the issue originally" step. No automation needed!

[Burhan İnegöl]

Eric,

You save my day,I spent 2 hours to find out your proper way to solve my problem.

Thank you.

[Jack Brickey]

Hi James welcome to the community. It appears that your WF is in draft. Please try publishing and recheck.

[James Wilhite]

Thank you, Jack. This was in draft when I opened it up to take the screenshot.  I've published a few different iterations of this workflow trying to get it to work.