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

Update initial ticket issue type when an issue of type X is linked

Caleb TeBokkel

I have two projects, a support project, and a development project.

Customer submits a ticket into the support project with issuetype "Support", issue A.

Development creates a ticket in the development project with issuetype "Bug", issue B, and links the ticket to the support project ticket, issue A.

When issue A, of issuetype "Bug", is linked to issue B I want to edit the issuetype of issue B to "Bug", using automation.

The automation should trigger when issue A is linked, and only if issue A is of type "Bug".

Please let me know if you have any ideas.

Accepted answers

Caleb TeBokkel

This is what I've tried. When issue is linked and the created issue is of project A, and type B, update the destination issue issuetype.

Automation 1.png

All comments

Caleb TeBokkel

This is what I've tried. When issue is linked and the created issue is of project A, and type B, update the destination issue issuetype.

Automation 1.png

Marc -Devoteam-

Hi @Caleb TeBokkel

I read that your initial issue is different the you show in the automation.

To summarise:

A customer raises a ticket on your support portal.
Development creates a "Bug" issue in their dev project
Links the "Bug" issue to the raised ticket on the portal
The portal ticket should be come issue type "Bug"

Is this correct?

Automation says it the other way around.

What is the issue type used for the request on the portal, is this also issue type "Bug", if this is no and you want to change this, this will break the connection to the Request Type on the portal and the custom won't be able to see the raised issue.

Can you clarify on what you exactly want to achieve?

Caleb TeBokkel

The above automation works as expected if I switch out the Edit: IssueType for Edit:Assignee (or any other field).

It looks like Jira is unable to edit the destination issue type if the source issue (the created Linked Ticket) does not belong to the same workflow. In this case, Issue A (destination issue) is part of a different workflow (although uses the same issuetype name called Bug), than Issue B (source issue / created linked ticket).

Marc -Devoteam-

Hi @Caleb TeBokkel

That is certainly so. I forgot to think this logical.

Caleb TeBokkel

Thanks for your assistance! I will submit a request to Jira to add the ability to change the destination issue issuetype even if it does not belong to the same workflow as the source issue.

Caleb TeBokkel

The above automation works as expected if I switch out the Edit: IssueType for Edit:Assignee (or any other field).

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management