Kristian Walker _Adaptavist_ Community Champion

Hi Jaynath, The issue appears to be with line 122, where you go to update the issue. ScriptRunner for Jira Cloud uses Unirest to make rest calls, so you should use Unirest rather than httpClient, which is not a supported package. I can confirm we have an example of updating a field on an issue here on line 32 that you can…

Hi Digvijay, The code for Summary is correct as Summary takes a string as input but the Description field requires you to provide the description in Atlassian document format. You can see details of what each field requires in the docs here. Fior setting the description we have an example in our Script Libray here that you…

Hi, It could be possible with Validators, but you would need an add-on out of the box to provide the ability to validate this, as I do not believe Jira has validators to do this out of the box. Regards, Kristian

Hi Aitrhira, I can confirm you could make a field required when option 1 is selected inside a select list field using the Behaviours feature provided by ScriptRunner for Jira Cloud. We have an example in our Script Library here, which shows how to do this. Please note that currently, Behaviours only works on Jira Software…

Hi Brian, I would advise checking if you have any other behaviours defined for that issue that could be hiding the field or any other plugins or automation that could be hiding that field.? I have just tested in my instance with a select list field and setReadOnly made it read-only as expected. If you can not identify any…

Hi Allan, I can confirm you could set a default description using the Behaviours feature provided by ScriptRunner for Jira Cloud. We have an example in our Script Library here, which shows how to do this. Please note that currently, Behaviours only works on Jira Software company-managed projects, as documented here. I hope…

Hi Jacob, I can confirm the ScriptRunner Connect tool could help achieve this requirement. ScriptRunner Connect is a web-based integration tool located here that allows you to connect your Atlassian instance to other tools in your organisation that have an HTTP based API, such as GitHub. With ScriptRunner Connect you can…

Hi Theresa, I can confirm that in Jira Cloud you can only use the issueFunction() JQL function provided by ScriptRunner on the Enhanced Search page as described in the documentation here. This is because Atlassian restricts how the JQL functions can interact with their infrastructure, meaning we must run them in a sandbox…

Hi JensH, I would advise using the Behaviours feature provided by ScriptRunner for Jira Cloud to set the summary on the create screen. This feature would allow you to set the value of the Summary field every time an issue is created so the user does not have to fill in this field. A script to do this would look something…

Hi Ivan, I can confirm you could limit issue types on creation to users in a certain project role using the Behaviours feature provided by ScriptRunner for Jira Cloud. We have an example in our Script Library here, which shows how to do this. Please note that currently Behaviours only works on Jira Software company-managed…

Hi Rowland, The issueFieldMatch JQL function in the Enhanced Search feature of ScriptRunner for Jira Cloud may help as this allows this matching field values based on a regular expression that you define. Regards, Kristian

Hi George, I am glad that solved the issue :). Regards, Kristian

Hi George, I can confirm with a Script Listener to access fields on an issue you need to call issue.fields. This means your line in bold should change to be like def currentAssignee = issue.fields.assignee.accountIdI hope this helps.Regards,Kristian

Hi Kauna, I can confirm the Behaviours feature of ScriptRunner for Jira Cloud currently only supports the create view and edit view, but support for the transition view will be coming in future, and I would advise you to keep an eye on the release notes to see when this is released. Regards, Kristian

Hi Jason, The only way to use the enhanced search functions in other features, such as Jira features like boards or confluence macros, is to save the enhanced search filter and then reference the filter using the syntax of filter="<FilterNameHere>". Unfortunately, there is no way to write the enhanced search functions…

I am glad this works and solves your issue :)

Hi Stephen, I cannot advise you on how to do this with Automation Rules, but I can advise you that if you use the ScriptRunner Plugin, the HAPI (Helpful API) feature will allow you to set Asset field values using the helper functions it provides. The documentation for this can be seen on the page here and may provide a way…

Hi Krishna, I do not know how to do this using templates, but I can confirm that the ScriptRunner for Jira Cloud plugin provides a Send Notification post function that you can use to send an email notification to certain users during a post function. You may be able to use this to achieve your use case of emailing…

We have our pipelines wait as we have the steps trigger the other pipeline, and this returns its result. If you have manual steps in a child pipeline, it would cause it to time out, I believe, but we do not use manual steps in child pipelines, so I am not sure what would happen with these.

Hi Jacob, I can confirm that in Jira Cloud you can only use the issueFunction() JQL function provided by ScriptRunner on the Enhanced Search page as described in the documentation here. This is because Atlassian restricts how the JQL functions can interact with their infrastructure, meaning we must run them in a sandbox…

Hi Patrice, I can confirm that in Jira Cloud you can only use the issueFunction() JQL function provided by ScriptRunner on the Enhanced Search page as described in the documentation here. This is because Atlassian restricts how the JQL functions can interact with their infrastructure, meaning we must run them in a sandbox…

Hi George, I recommend the Atlassian Trigger pipeline. At my company, we use a pipeline step in our pipelines to trigger each pipeline we need to trigger, and we run each step sequentially to get back the result of the triggered pipeline before running the next step. I hope this helps. Regards, Kristian

Hi-Light, Unfortunately, these messages cannot be customised and come from Jira themselves. I hope this helps. Regards, Kristian

Hi Christian, It is not possible with Jira Cloud to mandate a comment is added when an issue is added to a sprint, as there is no way to add a validator for this action. One workaround would be to use ScriptRunner for Jira Cloud and to add a Script Listener which ran on the Issue Updated event and in the script checked if…

Hi Thies, I can confirm that it is possible to set the description on the issue view (Edit screen), as in Jira cloud, the edit screen is the issue view. You can do that using the example script named Set default text in Description field. You will have to remove the if statement of if (!descriptionValueContent) { on line…

Hi Sy,I just did a test and came up with an example validator to mandate that an attachment is required when one of a list of specific option values is selected in a single list field.This example is in the file here, on line 85, and you can use it as a guide to help create the validator you require.If you need further…

Hi George, To get comments for an issue you can run a script similar to the script I have created here. I hope this helps. Regards, Kristian

Hi George, Thank you for your question. I can confirm the easiest way to see what value to set is to manually add a comment on an issue and then use the script console to make an API call to the Get Comments For Issue API to see what structure an at mention is stored as. I have done this and see it stored like below, where…

Hi Sebastian, Looking at the docs here it appears the Teams field is a special field that Atlassian provides which should have the ID customfield_1001 in all instances as it is a locked System field. The page mentions the field can be accessed via the Rest API but does not mention it can be used in Jira Expressions or in…

Hi Sy, That article you have linked to is for Jira Data Center and does not apply to Jira Cloud as the ScriptRunner for Jira Cloud plugin provides Workflow Validators using the Jira Expression Framework as documented in the Atlassian API documentation page located here or in the documentation page located here which…