Components automation - child issues

[Liron Bdolach]

Hi, 

Is there an option to prepare automation that allows me to create task/story/bug/subtasks dependent on components (or other custom fields)? (meaning that the component field in an epic will be duplicated to the child issue I will create)


Problem: 

I tried all automation I could think of but nothing works when I put it to test.

Example for what I'm looking for:

1. User creates an epic 1 with component X
2. User creates a task (=1.1) within epic 1
3. Task 1.1 automatically has component X in the fields
4. User creates sub-task within task 1.1 --> this sub-task also has the same components as the parents task, component = X

I would really appreciate your help or ideas here. Thanks!

[Trudy Claspill]

Hello @Liron Bdolach 

welcome to the community.

Are you working with Jira Cloud or Jira Server/Data Center?

Can you show us the automations you have already tried?

[Liron Bdolach]

Hi, I'm working with Jira cloud. I've tried so many, here are 2 that I tried.

Thanks!

[Bill Sheboy]

Hi @Liron Bdolach -- Welcome to the Atlassian Community!

When you trigger these rules (with issue creates) what do you see in the audit log details?  Please consider posting images of the audit logs as that may reveal what is happening.

And also: there is a known issue with Jira Cloud and the Issue Created trigger where the rule could start running before all of the data is available.  As a result, conditions and actions may not work as expected.  The work-around for that is to add a Re-fetch action immediately after the trigger to both slow the rule down and to reload the issue data.

Kind regards,
Bill

[Liron Bdolach]

Hi Bill,
Since I changed the automation so many times, I'm not sure how helpful it will be, but anyways - in the status, it says 'CONFIG CHANGE' many times.
This automation is supposed to happen the second I create a task/sub-task in an epic, and currently - it's not happening.

Thanks!
L.

[Bill Sheboy]

Hi, and thanks for that information.

That indicates the rule is not even triggering.  What is creating the issues: a person, another rule, an addon app, etc.?

If another rule is creating the issue, please look at the details for your rule and enable the setting "Allow Rule Trigger".  That will the issues created by the other rule to trigger this one.  Normally the rule engine prevents such triggering to prevent looping, errors, etc. but it can be needed in cases like this.

[Liron Bdolach]

Hi Bill, thank you, I appreciate your help!

Issues are created by a person.

I will try to describe the desired process - 

1. User creates an epic 1 and selects component X
2. User creates a task (=1.1) within epic 1
3. Task 1.1 automatically has component X in the component field
4. User creates sub-task within task 1.1 --> this sub-task also has the same components as the parent's task, component = X

Maybe it takes a while for automation to work?
The thing is that we defined 'components' as mandatory, so 'waiting' for the automation to kick in is not an option, as I cannot save any issue without adding a component to it.

[Bill Sheboy]

Thanks for clarifying your use case, @Liron Bdolach 

If the rule is not triggering and it is initiated by all manual/user actions, something else is happening.  Would you please post an image of the audit log for this rule, showing any details/errors?

And would you please confirm:

Are all of the issues for this rule (epic, task, etc.) in the same Jira project or multiple projects?

Is this a company-managed or a team-managed project?  You can determine that by expanding the options/settings on the left of the page and looking at the bottom of the tab.

[Liron Bdolach]

Thank you! 

1. All of the issues for this rule (epic, task, etc.) in the same Jira project.

2. It's a company managed project

[Bill Sheboy]

That information helps; thanks!  Please also post an image of the audit log details for when the rule runs and does not work as you expect.

[Liron Bdolach]

Sure. As you can see it says the rule was never activated. 

[Bill Sheboy]

For the first line in that log, it shows "No Actions Performed".  Please expand the Show More section on the right side to see that happened during the rule, and post that also.

If you were expecting that issue to process, please examine the issue's fields to learn why the conditions were not met.