Kristian Walker _Adaptavist_ Community Champion

Hi Katrin, I can confirm inside of ScriptRunner for Jira cloud that script listeners do not have a Project Role Updated event because Atlassian does not send a webhook event when an admin updates a project role. This means the closest you can do is to have a listener script which runs on the Project Updated event. However,…

Hi Sebastian, I have an example script console script located here, which shows how to create an Epic issue and then add a story inside of it for reference to help other people with the same question. Regards, Kristian

Hi Jesus, To create a table, you will need to use Atlassian Document Format and you can use the Atlassian document format builder tool mentioned in my post above to generate the Atlassian document format code for this. Regards, Kristian

Hi Autumn, I can confirm that you need to use Atlassian Document Format when setting the description field. Atlassian provides the Atlassian Document Format Builder tool, and you can use this to create the formatting you want in the visual editor. It will then generate the Atlassian Document format Code that you can paste…

Hi Sen, I can confirm that in Cloud currently, scripted fields show under a specific section for scripted fields, but we are currently working on making scripted fields actual custom fields. This will be released shortly, and you should watch the Release Notes pages to see when it is released. As for the script in Jira…

Hi Becky, I am glad we were able to help solve your requirement. Regards, Kristian

Hi Arunajyothi, I can confirm that, unfortunately, you cannot achieve this requirement with the Behaviours feature provided by ScriptRunner for Jira Cloud as it does not yet support transition screens. However, as a workaround, you can use the Workflow Validators feature that ScriptRunner for Jira Cloud provides to make…

Hi Uday, Unfortunately, Behaviours currently does not yet support Transition Screens in Jira Cloud but support will be coming for these later this year. Regards, Kristian

Hi C S Seshagiri, I can confirm that to achieve your requirement inside of Jira Cloud you will need to use the workflow validators feature provided by ScriptRunner for Jira Cloud. Workflow validators use the Jira Expression framework provided by Atlassian, and I can confirm we have some examples here to show their syntax.…

Hi Flavie, Unfortunately, this requirement is not possible to implement with ScriptRunner for Jira Cloud. The reason for this is that ScriptRunner for Jira Cloud uses the Jira Expression Framework provided by Atlassian for workflow validators and this does not allow querying how many issues have been created within the…

Hi Eric, Thank you for the feedback and for sharing your final solution. Just for reference, I have checked, and using the enhanced search Query Builder you can select custom date fields to use in the date compare function, as shown below. I'm glad we helped you get a working solution to your requirements. Regards, Kristian

Hi Becky, I can confirm that I have an example script located here using ScriptRunner for Jira Cloud which shows how to increment a number field by a specified value each time an issue is transitioned. This script should be run as a Run Script Post function as the Initiating User and can be used as a guide to help create…

Hi Noa, I can confirm the best way to achieve your requirement will be to use Behaviours for Jira Cloud. You will then be abel to configure a Behaviour script that fires on channge and sets field values when another field or group of fields changes to a specific value. I can cofnirm we have some examples here ,here and…

Hi C S Seshagiri, I can confirm if you are using Behaviorus provided by ScriptRunner for Jira Cloud then this currently does not support JSM Projects. This is why it works for Software projects and not JSM projects. For JSM support, we have a feature request here, and I would ask you to add your use case to it so that…

Yes this is just the text name you give the filter when you save it.

Hi Daniel, I can confirm to make issueFunction work in Jir Cloud, you need to use the Enhanced Search Page. Once you have defined your filter on your enhanced search page, you can use it inside regular Jira in places like filters, boards and dashboards by following the steps below. 1. Save the filter and share it (This…

Hi Yuri, I can confirm if you use one of the scriptRunner filters then you will need to define these on the Enhanced Search page as they cannot be used directly in the queries for the swimlanes on the board. Once you have defined your filters on the enhanced search page you can use it in the Swimalabns query by following…

Hi Sravan, In Jira Cloud as mentioned, you do not add a field as behaviours work differently due to the API's Atlassian provides. You specify the view where you want to run the behaviour on and then write your script, and we extract the fields which need to be updated when the script is saved. Please see a list of what…

Hi Sravan, I can confirm in Jira Cloud you do not specify the field when configuring the script, as we parse the script and set the affected fields automatically when the script is saved. To access a changed field, you can refer to the documentation here and may find the examples here and here useful. I hope this helps.…

Hi Eric, To define JQL to compare two dates, you cannot do this out of the box and will need to use a third-party app such as ScriptRunner for Jira Cloud. You can then use the Enhanced search page to define a query using the dateCompare function to return issues that match your calculation of end date" - "start date" > 90…

Hi Austin, I can confirm that inside of Jira Cloud Workflow Validators use the Jira Expression Framework provided by Atlassian. You must use the Jira Expression Framework syntax to write your validator. We have many examples here that show how to write validator expressions to help you write the validator you require. I…

Hi Dayand, I can confirm the best way to get the sprint start date will be off of an issue. If you are using Jira Cloud, we have an example of how to do this here that you can reference. If you are using Jira Server/ Data centre, then you can use the HAPI APIs to achieve this and we have an example here that you can use…

Hi Maggie, Usually, this occurs if a resolution is not sent on Done issues or the done status is not mapped to the last column of the board. The previous communtity post here and the Atlassian article here offer more detail on this that should help to resolve your issue. I hope this helps. Regards, Kristian

Hi Marco, I can confirm inside of ScriptRunner for Jira Cloud you can write a workflow validator to achieve your use case. Workflow Validators use the JIra Expression Framework in Jira cloud provided by Atlassian, and we have some example expressions located here to show how these work. Regards, Kristian

Hi Utsav, I can confirm that you can achieve this requirement using the ScriptRunner for Jira Cloud Add-on. The way that you would do this would be to configure a script listener, which would run on the Issue Updated event. The script would start by calling the Search for Issues API to run a JQL search to return the child…

Hi Cash, I am assuming here that you are validating a select list field. Instead of doing issue.customfield_11687.value != null you can just do issue.customfield_11687 != null to check if the field is empty. The reason for this is the field will not have a value property set on it until it has a value entered into it. I…

Hi Marcello, I think your condition needs to be like parentIssueInfo.body.fields.status.statusCategory.id The reason is that the status ID is below a statusCategory property. The way I found this was to run the rest of the call to get the parent issue on the script console and to look at what the status field structure…

Hi Yevgeniy, I can confirm if you just wanted to make the number field required when a value is selected in the Multi-select field on the Create screen, then you could use Behaviours from ScriptRunner for Jira Cloud to do this. We have an example behaviour script here that will help create a script to do this. With this…

Hi Jonson, In Jira Cloud this could be done on the Create Screen with Behaviours any of the custom field types supported as documented here. I hope this helps. Regards, Kristian

Hi Raju, I have tested this expression in my instance with a multi-line text custom field, and it works as expected. Can you please save the actual validator and run this as I believe it will run as expected when the workflow transition is run as the issue you are seeing is just the test not recognising the field type…