Greetings, I am using JIRA Software (cloud) and for one of our processes we need certain automation on the edit screen of the issue. Fields which would need automation: * f1 = Checkbox (5 options) * f2 = Drop down (5 options) * f3 = Drop Down Scenario: * After creation of the issues, relevant project owners / admin will keep entering the check boxes manually. * Depending on the number of check boxes selected, f2 will be updated. * Once all the check boxes are checked while updating the f2 field, f3 should be visible on the screen. * The user should be able to select relevant values from f3 Problem: * Since JIRA cloud does not support Behaviour option from the script-runner plugin, I am not sure where should I implement the script. * I think the APIs used on JIRA cloud is different than the APIs used on JIRA server. Therefore, I am not sure if the script written on server platform will work the same way on cloud environment. Please let me know if this is something that can be achieved on cloud JIRA. Thank you in advance. Regards, Pooja

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

Field automation on JIRA cloud

Pooja_Singh

Greetings,

I am using JIRA Software (cloud) and for one of our processes we need certain automation on the edit screen of the issue.

Fields which would need automation:

f1 = Checkbox (5 options)
f2 = Drop down (5 options)
f3 = Drop Down

Scenario:

After creation of the issues, relevant project owners / admin will keep entering the check boxes manually.
Depending on the number of check boxes selected, f2 will be updated.
Once all the check boxes are checked while updating the f2 field, f3 should be visible on the screen.
The user should be able to select relevant values from f3

Problem:

Since JIRA cloud does not support Behaviour option from the script-runner plugin, I am not sure where should I implement the script.
I think the APIs used on JIRA cloud is different than the APIs used on JIRA server. Therefore, I am not sure if the script written on server platform will work the same way on cloud environment.

Please let me know if this is something that can be achieved on cloud JIRA.

Thank you in advance.

Regards,

Pooja

Accepted answers

Kristian Walker _Adaptavist_

Hi Pooja,

Thank you for your question.

I can confirm that the ScriptRunner for JIRA Cloud plugin is unable to perform any dynamic validation on issue forms to link or hide fields like the server version can with the Behaviors feature.

Also, I can confirm that the plugin cannot dynamically populate field values or options like it can in the server version can with the Behaviors feature.

The reason we are unable to provide this functionality is due to the restricted functionality and API's which Atlassian provide inside JIRA Cloud, due to the fact that Atlassian only provides a Rest API in Jira Cloud and not the same Java API that the server version contains.

You can see more detailed information on the differences between ScriptRunner for JIRA Cloud and ScriptRunner for JIRA Server inside of the documentation page located here.

This means that unfortunately that your requirement of dynamically populating the options of the f2 field and then making the f3 visible once all options are selected cannot be achieved with ScriptRunner for Jira Cloud due to the reasons explained above.

Regards,

Kristian

All comments

John Funk

Hi Pooja - you might try Automation For Jira. It will not fire an action (like updating F2) until F1 is actually saved, not just updated as you click a box. But that might get you what you need.

Pooja_Singh

Hello @John Funk ,

The thing is we have already purchased JSU, Script runner and other bigger plugins and doesn't look like we will be opting for new plugins this soon.

Is it not something that can be achieved through script runner plugin?

It would be a great help if it gets resolved by script runner itself (although I will checkout this plugin for my reference).

Thanks & Regards,

Pooja

Kristian Walker _Adaptavist_

Hi Pooja,

Thank you for your question.

Also, I can confirm that the plugin cannot dynamically populate field values or options like it can in the server version can with the Behaviors feature.

You can see more detailed information on the differences between ScriptRunner for JIRA Cloud and ScriptRunner for JIRA Server inside of the documentation page located here.

Regards,

Kristian

Leonard Chew

Hi Pooja

There might be a hack-solution with Scriptrunner.

I'm not familiar with the cloud version, but if you have access to script fragments, you can inject javascript and css to your issue screen, meaning you can practically do anything on your GUI (client-side).

In this post, I have helped someone hide the "assign to me" link based on some data-conditions.

Maybe it helps, but then again... it IS a hack ;-)

Leonard Chew

... ah, sorry, it applies to the issue screen and not the edit screen, for which you are looking for a solution.

Kristian Walker _Adaptavist_

Hi Leonard,

Thank you for your suggestion.

I can confirm that the linked post above will only work on Jira Server as Jira Cloud does permit injecting JavaScript as Atlassian restricts this in Jira Cloud.

This means that Script Fragments are limited in ScriptRunner for Jira Cloud and in Jira Cloud work in their own Iframe and are not permitted to access fields or values on an issue.

This, unfortunately, means that as per my previous response there is no way to dynamically hide or modify fields in Jira Cloud with ScriptRunner for Jira Cloud.