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; } } }

Clone into separate project, then transition

Mark Hostetler_gz3foi

So what I'm trying to do is with a issue is created in Project A, clone that ticket into Project B. If the hotfix checkbox field is set to yes/on, then transition the Project B clone to a particular status.

When a ticket is created inside Project B, the rule runs fine, but when cloned from project A to B it doesn't take effect.

clone and transition.jpg

Accepted answers

Brydie McCoy (CB)

Hi Mark,

Sometimes if issues get into a strange workflow state the transition can fail. Can you transition the cloned issue manually via the UI? It is possible the problem is actually in the clone issue rule rather than the transition rule

It may be easier to create a support request and attach a screen shot of both rules and we can dig into the problem further.

Cheers,
Brydie [Automation for Jira]

All comments

Brydie McCoy (CB)

Hi Mark,

It may be easier to create a support request and attach a screen shot of both rules and we can dig into the problem further.

Cheers,
Brydie [Automation for Jira]

Mark Hostetler_gz3foi

I was thinking that it had something to do with the clone issue from the other project too...

It is certainly possible to manually move it to that status, we would like it to auto transition to the other status as its critical that it goes through an approval process.

I'll go ahead and open a support request.

Thank you,

Mark Hostetler_gz3foi

So follow up, turned out it was this little guy right here causing the problem. It needed to be checked on. allow rule trigger.jpg

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

addon-com.codebarrel.addons.automation