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

Automatisation to change issues types and status

Flavie Henry

Hello,

I want to create an automation to change issues types and status if it's A to F.

I tried different composition, but I still have the same mistake.

- Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status)

I tried to change issues types then the status or vice versa.

I have a company-managed project

Accepted answers

Trudy P Claspill

Hello @Flavie Henry

Please show us the complete automation rule you have constructed.

Also show us the complete details of the Audit Log entry for execution of the rule.

All comments

Trudy P Claspill

Hello @Flavie Henry

Please show us the complete automation rule you have constructed.

Also show us the complete details of the Audit Log entry for execution of the rule.

Flavie Henry

Hello @Trudy P Claspill

Yes, I didn’t find out how to do it on the first message.

Here are my last two tests:

Capture d'écran 2023-11-16 182333.png

Capture d'écran 2023-11-16 181747.png

Trudy P Claspill

Can you show us the Workflow diagrams for the two issue types? I want to see if there is a valid transition between "To Be Analysed" and "Accepted" for both issue types.

Is this rule scoped for a single project or multiple projects?

Flavie Henry

Yes, it's the both workflow diagram :

The first is the starting workflow and the second one we want them to go to. Today they are identical for the step, but we would like to reduce the first workflow to make the change between the two workflows. We were thinking about removing the Accepted step but maybe it wouldn’t be possible.

It's for multiple projects but on these workflows only.

Workflow_bug et improvement.png

Bill Sheboy

Hi @Flavie Henry

I recommend not changing issue types using an automation rule.

Jira provides a specific UI function to "move" an issue between types, allowing the application to ask any questions necessary to resolve problems. And it will prevent some moves when they are not possible. Automation rules do not have this ability to stop and ask guiding questions to the user, and so the change may work (or fail) with no indication of what happened in the audit log.

Instead please consider cloning the issue in the rule to the new type, and then abandoning or deleting the source issue.

Kind regards,
Bill

Flavie Henry

Hi Bill,

In our case this is not applicable, these are tickets created by the customer and it would be too complicated to inform these customers that their ticket numbers have already changed who manages their ticket on Excel.

Kind regards,
Flavie

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-software

jira-software-cloud