nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cloud automation when an epic is added to a ticket

Remi Preghenella

Hi,
I'm trying to automate the transition of a ticket when it is added to an epic using the following:

I've tried many options with the command "Field value changed" but none of them work.
According to the documentation, I could also use a regular expression to match the field name that is changed but it doesn't let me validate my regex.

Any help would be greatly appreciated.

Thanks,
Rémi

Accepted answers

All comments

Mark Segall

Hi @Remi Preghenella - You're on the right path with the Field Value Changed trigger. Just make sure the field you're working with is one of these two depending upon the type of project you're working with:

Epic Link field (Company Managed project)
Parent field (Team Managed project)

Remi Preghenella

Hi @Mark Segall
Thank you for the reply.
As I use a Team Managed project, I've based the Field Value Changed trigger on Parent Link.
However, the rule is never triggered!

Using the API, I can see/confirm that the issue is updated and a parent is added.

The rule is super simple so I wouldn't expect any issues:

Mark Segall

Hi @Remi Preghenella - Team Managed projects will use Parent. Parent Link is something entirely different:

Parent - Used for linking Sub-Tasks to Stories/Tasks/Bugs and for Team-Managed projects, Stories/Tasks to Epics
Parent Link - This is specifically used by company managed projects that are utilizing Advanced Roadmaps to create a hierarchy of issues above the epic.

Remi Preghenella

I don't have the Parent option though in the list of fields.

Thx

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud