Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Post Function Not Working on Sub-Task Workflow for Assignee

Edited

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?

 

 

Screen Shot 2020-05-26 at 4.00.50 PM.png

2 answers

1 accepted

1 vote
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 27, 2020

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.

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
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 28, 2020

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

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
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 04, 2020

Glad it is working for you!

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
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 08, 2021

Hi Daniel,

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

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

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
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 25, 2021

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. 

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
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 22, 2023

Eric,

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

Thank you.

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 26, 2020

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

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. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events