Emmanuel Katto : Automation Based on Custom Field Options for Projects

[Emmanuel]

Hi everyone,

I'm  Emmanuel Katto, have a custom field called "module" that holds different values depending on the project. For example, in project "X," the options are A, B, and C; in project "Y," the options are B, C, and D; in project "Z," they are C, D, and E, and so on.

I need to set up an automation where, when an issue is opened in one project, the automation will check the "module" field value. Then, it should create (or clone) the issue in other projects that share that value in their context.

For example, if the original issue in project "X" has the value "B," the automation should clone the issue in project "Y" (because project Y has "B" as one of its options).

Is this possible? I'm having trouble setting up the condition to check the field’s options, especially since the available options in the "module" field change regularly as new ones are added.

Any suggestions on how to approach this or if it's even possible would be greatly appreciated! Thanks in advance!

Regards

Emmanuel Katto

[Jack Brickey]

Hi @Emmanuel , I don't believe you can dynamically check the context with an automation. This would mean you would have to "hard code" the solution using an If/else component. Obviously, this is less than ideal if the values within your various contexts actually change regularly. However, if they do not, then it should work perfectly fine.

[Bill Sheboy]

Hi @Emmanuel 

What have you tried thus far to solve this need?

If you have a rule which is not working as expected, please post images of the rule, its actions / conditions, the audit log details, and describe what is not working as expected.  Those will provide context for the community to offer suggestions.

If you have not yet started a rule, I encourage you to try to do so.  Successfully using automation requires learning and experimentation.  To help you get started, here is one possible approach...

As you describe a custom field with the same name, "Module", being used in multiple projects with different selection options, I hypothesize these are each team-managed projects.  And so from a Jira configuration perspective, each field is separate and distinct.

And you describe the values of the fields change regularly as new options are added.

As long as values are only added to the fields (and never removed) one could use the REST API to solve this, dynamically identifying any changes to the fields involved. The general approach would be:

• using the Send Web Request action, call the REST API endpoint to get the field options for the "Module" field in project "X"
• ...repeat that for each possible project, saving the option results in created variables
• use the if / else block with the Smart Value Condition and regular expressions based on the variables to decide to which project to clone the issue

Kind regards,
Bill

[Valerie Knapp]

Hi @Emmanuel , thanks for your post.

I am making some assumptions here, like that these are all company-managed projects and global custom fields and that you mean to say you have different custom field contexts.

I would start / try with a branch, something like this.

So, the trigger is on the issue creation. I would put a condition that the Module field is filled in.

Then, you can branch on the JQL for when the Module is indicated as some value, to clone and create the issue into the specific project, and then do the same thing for each option of the Module.

Please try this out and let us know if you have other questions or doubts.

Cheers