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!
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:
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.
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?
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.