Kristian Walker _Adaptavist_ Community Champion

Hi Bloomingbridges, I have clicked the 'Request Assistance' button to notify Atlassian Support, so they can review this post and respond to you. I hope this helps. Regards, Kristian

If this solution solved your requirement Omer can you please accept the answer so that other users looking for the same requirement can see that it is correct. 

I am not sure, but Atlassian Support will be able to advise what is needed when they review this request.

Hi Ken, I have clicked the Request Assistance button for you to flag your request to Atlassian support so that a member of the Atlassian Support Team can review this request for you. I hope this information helps. Regards, Kristian

Hi Codeminds, I have clicked the Request Assistance button for you to flag your request to Atlassian support so that a member of the Atlassian Support Team can review this request for you. I hope this information helps. Regards, Kristian

Hi Jon, I have clicked the Request Assistance button for you to flag your request to Atlassian support so that a member of the Atlassian Support Team can review this request for you. I hope this information helps. Regards, Kristian

Hi Ramesh, The Epic Status field is a system field used b Atlassian to determine how the Epic is displayed in the Epics panel on board as mentioned here. The Status field is the regular status field mapped to the workflow used by the Epic Issue type. I hope this information helps. Regards, Kristian 

Hi Omar, I believe you can simplify your validator to be like the one below and this should allow any value less than 10 or 10.0 in the field. issue.customfield_12082 != null && issue.customfield_12082 <= 10.0 Hope this helps. Regards, Kristian

Hi Maruthi, It is possible to achieve your requirement in Jira Cloud using the setOptionsVisibility() method that Behaviours in Jira cloud provides. We have an example here that shows how to restrict field options when a value is selected in a multi-select list field. We also have an example here which shows how to check…

Hi Vikrant, I have checked, and the issue type field does not support having the description set on the Create view as the Atlassian docs state here, so this means it is not possible to set the description below it. It also mentions this in our documentation page I linked in the previous post and I was looking at the wrong…

Hi Vikrant, I can confirm that the Project system field is not supported by Behaviours inside of ScriptRunner for Jira Cloud and this is the reason your script is not working. You can see a list of what fields are supported per view in the documentation page here as a reference. Custom Project Picker fields are supported…

Hi @Don Coles I have flagged this issue by clicking the Request Atlassian Assistance button for you, so Atlassian support can see this and investigate it for you. Regards, Kristian

Hi @Dana Morgoch I have flagged this issue by clicking the Request Atlassian Assistance button for you, so Atlassian support can see this and investigate it for you. Regards, Kristian

Hi @acheung012 I have flagged this issue by clicking the Request Atlassian Assistance button for you, so Atlassian support can see this and investigate it for you. Regards, Kristian

Hi, Unfortunately, there are no other APIs, so getting users' email. What you are seeing is the behaviour that is intended, where users can hide their email due to GDPR regulations, and this is why Atlassian added account IDs so users could choose not to show their emails, which is considered PII. This means you can only…

I can confirm we are working on support for Jira Service Management projcets in Behaviours and this will be coming in 2026 and I would advise following the feature request here to see when JSM support is released for behaviours. Kristian 

Hi @Inayatulla Shaik We have checked from the ScriptRunner side and noticed an issue with the type definitions not correctly recognising some fields in the Behaviours code editor, and have just released a change to fix the issue. Can you please refresh the page and see if they show as expected? If not, please notify the…

Hi Sohail, As Mercy has mentioned, you can use the Enhanced Search feature of ScriptRunner for Jira cloud and then use the subTaskOf() search function to create the filter you need. I hope this information helps, Regards, Kristian

Hi Inuyata, Please note that Behaviours inside of Jira cloud do not support all custom field types and only support fields that Atlassian supports in the UI modifications API, which it uses. You can refer to the documentation page here for a list of supported custom fields. I hope this answer helps, Regards, Kristian

Hi James, In Jira Cloud, if you click the settings Icon and then select Work Types >> Workflows. When you view the workflow in the old workflow editor, you will see an export dropdown, which you can click on to export it as shown below. This will allow you to export workflows used by Company Managed projects, and there is…

Hi Leslie, If you have ScriptRunner for Confluence cloud, then you could achieve this requirement using a Script Job. This would allow you to schedule a script that would run on the specifed schedule and add labels to the archived pages returned by a CQL We have an example script here that shows how to add labels to…

Hi Rahul, If you have ScriptRunner for Jira Cloud installed, then you could create a Scripted field to calculate the value and store it on an issue. You could write a script to check the changelog and get the times out of this since the issue was created til it transitioned to done. We also have some examples here that…

Hi Geethanjali , If you have ScriptRunner for Jira Cloud installed then you could use a workflow validator to block the transition of the work item when its linked item is not in the done status. Workflow validators use the Jira Expression framework which is documented here and you can use this documentation to see how to…

Hi Waki, If you have ScriptRunner for Jira Cloud installed then you could use a workflow condition to block the transition of the work item when its linked item is not in the done status. Workflow conditions use the Jira Expression framework which is documented here and you can use this documentation to see how to create…

Hi Arieli, 1. The only way to see who uses them in DC would be to add a log to log out who is triggering them, as Rik mentioned. 2. There is currently no alternative in ScriptRunner for Jira Cloud directly, but you could use the ScriptRunner Connect tool to recreate these that can be called from ScriptRunner for Jira Cloud…

If you use ScriptRunner for Jira Cloud the example here shows how to create a calculated field which shows how long an issue has been in its current status. 

Hi Tomasz, If you have the ScriptRunner for Jira Cloud plugin, then the Behaviours feature can achieve this use case. Using behaviours, you can hide fields using the setVisible() method on the create view or issue view, and you can do this based on whether users are in a specific group or project role. We have some…

Hi Digvijay, I am glad you were able to meet your requirement and that the expression generator helped you address this request. Regards, Kristian

Hi Digvijay, Unfortunately, you would not be able to do this with Behaviours as behaviours in Jira cloud does not support setting errors on a screen. You could do this with a workflow validator on the Create screenwhich would allow you to set an error message. Using a validator, you could write a Jira Expression to verify…

Hi Nick, I can confirm in both ScriptRunner for Jira and Confluence cloud that we don't provide any public APIs for creating config programmatically. This means currently you can only create this via the User Interface in the apps. I hope this helps, Regards, Kristian