Kristian Walker _Adaptavist_ Community Champion

Hi Leo, 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 Harrison, Yes, that is correct. Validators can not be used in Team Managed projects, as Team Managed projects in Jira do not support customising the workflow. You should be able to set up approvals in Company-Managed projects, and the Atlassian page here provides a guide on how to do this. I hope this helps. Regards,…

Hi Fabian, Unfortunately, Enhanced Search does not provide any functions for querying groups, so this requirement will not be possible with Enhanced Search by ScriptRunner in Jira Cloud. You can, however, achieve this partially out-of-the-box with JQL in Jira using the members query. You can do a query like below, where…

Unfortunately, this use case is currently not possible inside Jira Cloud with ScriptRunner as behaviours in Jira Cloud do not support JSM due to Atlassian not yet supporting this in the UI modifications API, which behaviours use. 

Hi Chamadri, It is possible to achieve this requirement with ScriptRunner for Jira Cloud. I don't have an example script on how to do this, but you will need to use the Jira Data Center rest APIs and call these from your script. You would need to use the Get Issue for Key API and call this from within ScriptRunner for Jira…

Hi Richard, It is not possible to pop up windows with ScriptRunner or Automation as Atlassian do not provide any APIs to do this. This means you will need to add the label via a Script Listener with ScriptRunner, as Helmy has said, or using Automation, as Aron has said. Regards, Kristian

Hi Corine, Yes, the parameters required have changed since this original question was asked. If you still have issues, a support ticket will be required so they can help investigate the issue in your instance further. Regards, Kristian

Looking at your error, I see you have not filled in the text to match as the first parameter, and this is why your expression is invalid. Checking the docs for issueFieldMatch, the parameters to provide are: issueFieldMatch(Subquery, FieldName, Pattern Match) This is why you get the error when the subquery is not present.…

Hi Luis, Unfortunately, I am not aware of any way to display a pop-up dialog in Jira Cloud. The reason for this is that Atlassian does not provide any REST API that Scripts, plugins or even Jira Automation can use to display a pop-up dialogue. I would advise adding a link to the form in JSM, which can open a Confluence…

HI Corrine, For this issue can you please raise a support ticket here, and our support team will help to diagnose this issue. Regards, Kristian

A recording of the webinar can be viewed here for anyone who was unable to attend.

Hi Aggeliki, There is no way out of the box to reduce the length of a custom field out of the box. As a workaround, you could use an App from the marketplace, such as ScriptRunner or JWME, or any other marketplace app that provides validations to ensure users don't enter more text in a field when an issue is created. I…

Hi Vikrant, I have an example script here which can be configured as a Script Listener and shows how to use the Rest API to clear field values when they are cloned. You can modify this example to specify the name of your Number field and cascading select list field, and set it to null to clear the values. If you need…

Hi Ana, I can confirm that if you are using ScriptRunner for Jira Cloud, then you can achieve this use case using the Behaviours feature. You can see what fields and methods Behaviours supports inside the documentation page located here. Also, we have an example of how to make fields required based on a value in a select…

Nice write-up, Ana. Thank you for sharing this use case, and you solved it using ScriptRunner.

Hi Sachin, I can confirm you can solve this requirement using a Workflow Validator inside of ScriptRunner Jira Cloud. The example on line 93 here shows how to validate that an issue cannot transition until all child issues matching specified link types are in a certain status. You will be able to update this to achieve…

Hi Sachin, You could achieve this use case using ScriptRunner for Jira Cloud. To achieve this use case, I would advise using a Script Listener. Using this feature, you can configure it to run on the Issue Created event and add a condition in the conditions box to make it run for only specific issue types. We have an…

Hi Koushik, I can confirm that if you are using ScriptRunner for Jira Cloud, then you can achieve this use case using the Behaviours feature. You can see what fields and methods Behaviours supports inside the documentation page located here. Also, we have an example of how to make fields required based on a value in a…

Hi Richard, The Jira Expressions documentation page here shows what properties you can call on an issue, and unfortunately, there is no remote links property, which is why you are getting the error you are seeing. As Atlassian doesn't provide a property for this, then it will not be possible to validate that links to…

Hi Ewa, As Trudy mentioned, you can achieve this use case by adding a default description and then using Behaviours. We have an example of how to do this here that you can refer to as a guide. Regards, Kristian

Hi Angel, It is not possible to search with workflow validators to search for all other issues in the project to validate if any other issues exist, which means this requirement would not be possible to achieve within Jira Cloud. Regards, Kristian

Hi Tu, If you have ScriptRunner for Jira Cloud installed you can also write a Scrtipt Listener to send a notification to Slack when an issue is updated. We have an example here which shows how to send a Slack message when the priority changes on an issue that you can refer to as a guide to help you to create the script…

Hi christa, If you are using ScriptRunner for Jira Cloud then you can use the Behaviours feature to hide description text. The way you would do this is to configure a behaviour on the view you require that uses the setDescription() method and sets the description to an empty string for the fields you require. I hope this…

Thank you for this, Drew. Once it is supported in UI Modifications, then we will look to add support for it in Behaviours. Regards, Kristian

HI Drew, We have a feature request board located here that you can raise your use case to, so the product owners see it. The field's behaviour support is the one Atlassian supports in the UI Modifications API, which it uses, so Atlassian would need to support these before they could be added to behaviours. Regards, Kristian

Hi Deepak, I have created a sample script which shows how you can find this information in Jira Data Center with ScriptRunner using the HAPI APIs. The script can be seen here and uses the approach Leo mentions above to find the project keys. Note that the script returns 1000 issues at a time, and if you need more, you can…

Hi Michael, This question was answered previously in the thread here, so I would advise reviewing this to see the differences between the two products. Also the blog here gives a good comparison of the differences between the two products that you may find useful. Regards, Kristian

Hi Alicia, It looks like you have configured a team-managed project rather than a company-managed project. The docs you linked to are for company-managed projects, as team-managed projects are lightweight projects and do not support adding custom fields to cards. You will need to create a company-managed project by…

Hi Drew, I can confirm that Behaviours in Jira cloud only support the field types documented on this page. Unfortunately, Advanced Roadmaps fields are not supported, as behaviours only support the standard Jira custom field types documented in the page above. This means you will not be able to write a behaviour based on…

Yes, behaviours only work on views that Atlassian has enabled the UI modifications API for, which are currently the Create Views, Issue View, and Transition View. They support the issue view in multiple places such as on boards as documented in the page here, but automation would still be able to create issues and work…