Kristian Walker _Adaptavist_ Community Champion

Hi @Denise Wermager , I have created an example script, located here, that can be used with Behaviours for Jira Cloud and demonstrates how to restrict values in one Multi Select List field based on values selected in a second Multi Select List field. In this example, you just need to update the IDs for your custom fields…

Hi Kottu, As Christos said, there is no way for the work logs screen to dynamically check if the number of characters entered is a certain amount. With ScriptRunner for Jira Cloud, you can use a workflow validator to prevent a transition if the worklog is not entered in a transition. A validator would also ensure that…

It is now possible with behaviours to restrict issue type options inside of Jira Cloud, and we have an example script that shows how to do this here. 

It is now possible with behaviours to restrict issue type options inside of Jira Cloud and we have an example script that shows how to do this here. 

Unfortunately, it is still not possible to fully build this project in Jira Cloud as all the APIs to copy all project features do not exist in Jira Cloud. The closest workaround is to call the Create Project Rest API to create a project and specify the IDS of existing items, like schemes. An example of how to use this API…

Hi Daniel, I can confirm that, currently, there is no way to share common code in Jira Cloud. However, we are working on a feature called Script Manager, which will allow you to store code in files that can be reused across features. This will be released in the near future, and you can monitor the release notes to stay…

Youre welcome :)

Hi Ariel, I can confirm that in Behaviours for ScriptRunner Jira Cloud you must set the label field using an Array of strings e.g ["label-1","label-2"] as described in the UI Modification API documentation page here. You can also see the structires to use to set field values inside our documentation page here and this will…

Hi Jayanth, Setting the description with behaviours uses the Atlassian document format, and it is possible to set checkboxes with this, as the description field supports this. One way to visualise the structure is to use the Atlassian document builder tool, which generates the necessary syntax. Using this, I have created…

Hi @arielei I have a sample script which I have tested on Jira DC version 10.7.4 with ScriptRunner version 9.24.0 and this script can restrict global custom field contexts for specified fields to a set of specified project keys. The script can be seen here and I would advise that you take a clone of your instance and test…

Hi @Donamol N C , Yes Behaiours is now available inside of Jira Cloud and you can see what fields and methods are supported inside the documentation page here as well as some example scripts for the cloud version here. I hope this helps. Regards, Kristian

Hi Guido, Unfortunately, the Attachment Created event does not provide the Issue Key in its bindings. The reason is that the webhook event is sent back when an attachment comes from Atlassian, and they don't provide the issue object in the event they send back. This means you won't be able to get the issue key. You'll need…

Hi Gaetona, Validators inside of ScriptRunner for Jira expression framework. It sounds as if the group is not correctly configured for users, which is causing the validator to fail. I would advise you to raise this as a support request here, so that the ScriptRunner support team can help debug the validator and identify…

Hi Lakshmi, There is no way to do it globally via ScriptRunner, unfortunately. This means using ScriptRunner, you would need to write a script that loops over each filter and updates it as I suggested. It may be possible to write a script via the database to find all filter values and bulk update them, but you would need…

Hi James, Yes, for fields like description, where Atlassian switched to ADF, you will need to use V3 of the rest API, like in my example. I am glad you managed to get your script working. Regards, Kristian

Hi Christian, The Behaviours feature of ScriptRunner for Jira Cloud can help to achieve this use case of adding default text to the description field. We have an example script of how to do this here that you can use as a reference guide. I hope this helps. Regards, Kristian

Hi James, I can confirm it would be possible to achieve this requirement using behaviours in Jira Cloud. To do this, you would need to write a script that first fetches the issue you want to get the description from. We have an example of fetching fields from an issue here that you can use as a reference. In this example…

Hi Lakshmi, ScriptRunner could help. To do this, you would need to follow the steps below. I have given steps for both Jira Cloud and Data Center. Data Center Steps: For Jira Data Center, you would need to write a script to get the filters your user has permision to see using the Find all filters HAPI API. You would then…

Hi Digvijay, Could you please raise a support request here and the ScriptRunner support team will be able to investigate and debug these errors for you. Regards, Kristian

Hi Bharat, The documentation page here includes examples of workflow validators that can help you create the validator you require. This page has the Linked Issues examples, which show how linked issues of a certain type have a specific resolution and how you can modify this to achieve your use case. Also, you can see a…

Hi Digvijay, I have created a small example here that runs on the Issue View and the On Change event. It hides values when a certain value is selected in a checkbox field and makes them visible when a different value is selected. You can use this as a guide to help create the script that you require. I hope this…

Hi Digvijay, I can confirm that behaviours for Jira cloud supports making fields hiding and showing fields based on another value. We have an example script located here which shows how to do this and this could be modified to achieve your use case. I hope this information helps. Regards, Kristian

Hi Digvijay, I cannot give a timescale as to when, as in Cloud Behaviours, we will use the UI modifications API from Atlassian, so we can only support fields that Atlassian supports in this API. If Atlassian add support for this field type, then it will get added to behaviours. Regards, Kristian

Hi Digvijay, I can confirm that behaviours for Jira cloud only supports the fields documented here for the issue view screen and Message type field is not supported which means your requirement will not be possible. However, I can confirm for checking a workflow status and user group in a script you can see examples of how…

Hi Stefan, You are correct, there is no way to find users who have no issues assigned to them via JQL, and this would need to be done via a script. Unfortunately, if this is the case, you won't be able to get the script's output on a dashboard. A possible workaround would be to make an API call to put the data returned…

Hi Assem, Unfortunately, ScriptRunner will need to make an API request to Gitlab to get this information, so if you cannot make an API request, then this means your use case will not be possible. Regards, Kristian

Hi Angel, If you are encountering issues with this script, then can I please ask you to raise a support request here so that the suppport team can debug any issues with the script. Regards, Kristian 

Is this being done on Jira DC or Jira Cloud? If Jira DC you can use the JQL functions in a JQL query in the main search page, if it is Jira Cloud you need to create the filter on the enhanced search page and then call the shared enhanced search filter in a QL query on the main search page.

Hi David, Unfortunately, in Jira Cloud the Behaviours module does not provide setError() function so this means your use case cannot be achieved. The reason for this is that Behaviours in Jira Cloud uses the UI Modifications API from Atlassian, which does not provide a setError() method. You can see what methods the cloud…

Hi Vitheya, The issue key in Jira is auto-created based on the project key and the next number sequence available for the project. This cannot be overridden and changed as Atlassian does not provide any APIs to do this. Regards, Kristian