Automation for Jira - Identify is a ticket exists or should be created

Adrienne McCoy

Hello,

I am using Jira Server.

I need to create an automation where I create a ticket in one project, project A.

There will be an ID # on the ticket (which will a free text field).

 

I also need a ticket in project B. There are two scenarios:

1. A ticket in project B does already exists, in which the newly created ticket in project A will link to it - and it will recognize that it exists by the ID #.
2. A ticket in project B does not already exist, in which automation for jira will create a new ticket in project B - recognizing that a ticket does not exist by using the ID #.

Is this possible?

I truly appreciate any help or direction!

Best,

Adrienne

 

Curt Holley

Hi, may I just check I have your scenario right?

Are you saying you always need a ticket (with the same opportunity ID) in both Projects A and B? 

or

You need to have matching tickets in A and B only when an opportunity ID is present?

or....something else?

Another question. Is one project considered the master (where the content should be created)?

One issue perceive with using a free format field as the unique identifier for automation is; How will  this field be controlled? as people can put anything into it. This could lead to automation creating and or linking tickets and creating redundancy, confusion and overhead (to tidy up).

That said, this should be doable with automation. But the free format field as the unique ID at the centre of it.....worries me.