In JIRA I want to automatically add a developer to a sub-task, I think this can be done in two ways with:
However there is a problem with both ways. For the first method (which is preferable), the problem is that there is no option in JIRA Automation that support to automatically assign a sub-task to the same assignee as the parent task/story/bug. Or am I missing something?
The second method is problematic because in my case it's not the person who triggers the transition, but it's Bitbucket (by creating a branch or creating a Pull request). JIRA automation does not recognise this, and therefore doesn't assign a developer to the sub-task(s).
Do you have any suggestions on how I can setup JIRA Automation for this?
Thanks in advance!
Hey Peter,
This should be fairly easy to do and as you mention the first is preferable (and the only way to do it Automation for JIRA).
Currently, the Edit Action is more powerful than the Assign Action and it has an option to copy the assignee from the parent.
I'd create a rule that looks like:
image2017-1-5 12:0:33.png
This rule is made up of:
You can use Conditions to restrict what kind of issues this is done for.
Let us know how you go.
Cheers,
Nick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nick, I don't see that "Copy from Parent" drop down in my Edit Issues Component. What am I missing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
Can you post a screenshot please of what your 'edit issue' action looks like? Also can you ensure you are running the latest version of Automation for JIRA please (if you are in server)?
Cheers,
Andreas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Nick Menere ,
The option you provided works well in a straight forward scenario. However, I need your assistance in another scenario.
Considering a slightly different scenario, where the assignee is now copied to the Sub-task from the parent, but the automation rule has to do it only once.
Meaning, the rule should apply to the Sub-task only once. The next time when the parent issue assignee changes, the sub-task should not pick that value, and keep the current assignee value intact. Is this possible at all?
Best Regards,
Rahul Savaikar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know it's a bit late, but for future reference:
It is possible if you want to accomplish this task on creation of the subtask by simply using another trigger, i.e. "Issue created"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello I am hoping someone can assist me with this rule. I am fairly new to automation
I am not sure why this rule is not working for me.
I am expecting the subtasks below to be populated with the assignee of the parent
I would appreciate any assistance as to how I can get this automation to work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nick - I have created (and Published) the same exact rule as above, but when a dev creates a sub-task in an existing task, the sub-task is still not assigned to the dev (as the parent). The sub-task is still assigned to the project lead.
Any ideas?
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the assignee is not on the Create screen it may cause issues and not assign correctly. Is the assignee on the create screen?
Cheers,
Nick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Nick!
The Task is assigned to Dev1 at some point in the project. Later, Dev1 is creating technical Sub-tasks within the above named task, but the sub-tasks do not get assigned to Dev1, they get assigned to the project lead (me).
I'm not sure what Create screen you are referring to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.