Automation to sync the status of ideas and epics

[Emerson]

Hi, everyone!

I'm trying to build an automation that changes the status of epics to "DISCARDED" or "ABORTED" when I update a Product Discovery idea to the same status.

DISCLAIMER: The sync when I change it to "DISCARDED" already works fine, but the change to "ABORTED" doesn't work yet.

[Bill Sheboy]

Hi @Emerson 

Jira Product Discovery (JPD) Ideas connect to their "discovery tickets", such as Epics, using issue links and not the parent / child relationship.  Please try using linked issues branch for the correct type to find the Epics.

Next, you are trying to detect changes in the JPD project to update issues in other project types, such as a software project.  And so the rule scope must be multiple-project or global.  Your Jira Site Admin will need to help do that from the global automation settings.

Kind regards,
Bill

[Emerson]

Hi @Bill Sheboy

I made this change you suggested, and the same thing happened. For some mysterious reason, it doesn't recognize the transition to "ABORTADO" and doesn't move the epics. And automation has been global since the beginning.

[Bill Sheboy]

Please post images of the updated rule and of the audit log details showing the execution.  For the log, remember to expand all of the areas at the right side to show the details.

[Emerson]

Here it is

[Bill Sheboy]

For that first rule execution, please expand the details on the right side with the two > areas, and then repost the image.

Until we see that...

The log seems to indicate either the branch found no issues or the condition was not met.

[Emerson]

[Bill Sheboy]

My apologies if I was unclear: please also post the audit log details with the areas expanded.

The recent changes to the audit log make it difficult to see what happened unless all of the areas for a log entry are expanded with the arrows > at the right side.

[Emerson]

[Bill Sheboy]

The log shows the condition did not match.  And as the rule is written...

• trigger: issue transitioned to one of the two status values
• branch over any issues linked to the trigger issue (the Idea)
  • for each of those (the Epics)
    • only continue when there are no issues linked to the Epic in the status values in the JQL

Based on your original question, that does not seem to be what you wanted.  Perhaps try this:

• trigger: issue transitioned to one of the two status values
• condition: issue type is Idea
• branch over linked issues: for type "is implemented by"
  • condition: status not in your two status values
  • action: transition the issue