Many Cloud instances (Cascading custom field trigger)

Originally asked by George Smith on 14 August 2023 (original question)


We have a Jira Cloud instance syncing with 5 other Jira Cloud instances. The way the trigger works right now is that it reads a specific custom text field for the project name that the remote issue is supposed to be created in. This means we have 5 custom text fields.
Can we leverage a cascading custom field with the first level being the instance name, and the second level being the project within that target instance? how do we do this?
Also, what would the trigger look like then?


Answer by Syed Majid Hassan on 24 August 2023

I used a cascading select field in source Jira called City. Based on the value of this field, the ticket gets automatically exalted to Jira2 or Jira3 (depending on value).

A short video explanation is attached here:


This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.