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

Create a Workflow linked with 2 projects

Pierre-Henry Deliège

Hello there,

Let summarize my environment:

I have 2 Jira projects: one for customer support/request and one for the Dev.

Once a customer opens a ticket on customer support, I create a new ticket on the Dev project so Dev Team can follow it and includes the issue/new request in the development.

This new ticket on DEV is linked to the ticket on Customer Support.

On the customer support project, I'm using the standard workflow: Waiting for support / Waiting for Customer.

I would like to have a third status: Development in progress. This status should come automatically when the ticket opened on Dev project is on status TODO.

I've tried multiple things following some readings, but it still doesn't work.

Any support to create this new workflow will be much appreciate.

Thanks in advance,

Accepted answers

Pierre-Henry Deliège

Dear all,

Thanks for your support and your ideas.

I finally found the issue (with the help of the great Altassian support).

In one of my transitions, I had a condition that was never met.

Now, it's working fine !!!

Thanks again for your support.

All comments

Gezim Shehu [Communardo]

Do you have ScriptRunner or any similar script running addon?

You could write a simple script, only for that link type preferably, and transition linked issue automatically.

Service Desk by default offers some of this functionality, but very limited.

Strongly suggest to get ScriptRunner.

Pierre-Henry Deliège

Hello,

Well, here is what I setup:

My Workflow:

Then I created an Automation:

The automation is working fine as soon as I modified the linked issue, but I have the following error:

What am I missing ? Where can I find more information about this error ?

Thanks for your support.

laralg

Pierre do you have a field thats suppose to be filled or mandatory in that transition? If Jira is specting an field or validating information in that transition the automation will not be able to take place.