Kristian Walker _Adaptavist_ Community Champion

Hi sciencecovskij , Changing the user to the add-on-user is fine to run the script is fine and is a good way to ensure the script works. When run as the initiating user and the error occurs this means there are some permissions with the user executing the script not allowing them to access the issues, and I would advise…

Hi Zaldy, Unfortunately, as Behaviours in Jira Cloud does not yet support Jira Service management, your requirement will not be possible as no other ScriptRunner features can show or hide fields. The reason we cannot JSM currently is that Atlassian does not support it in the UI Modifications API, which behaviours runs on.…

Hi Kannpitcha, I can confirm that in scriptRunner for Jira Cloud we work with Rest APIs only and that it is possible to write scripts that would interact with an external application such as Slack, as long as the application contains a REST API which can be called to interact with it. We have an example in our library…

Hi Todd, I can confirm we have an example validator located here on line 59, which shows how you can validate that a checkbox field has one specific value selected and that a single line text field is not null. You can take this validator and use it to help create the validator you need to solve your requirement. I hope…

Hi sciencecovskij , I can confirm this error can occur when an issue returned in the JQL query has some form of permissions, such as an issue security scheme, which means the JQL search cannot access it. I would advise checking the issue security schemes and project permissions to ensure the user that the script is being…

Hi Murat, I can confirm that when you run the script as the ScriptRunner add-on user, then this will return this user, and the script will be triggered as this user. The only way to make it be set to the person who ran the script is to run the script as the initiating user, as the app does not support running as the…

Hi Kelly, I can confirm ScriptRunner for Jira Cloud's behaviours feature will support working on the issue view, which is the edit screen in Jira cloud in the near future. This would allow fields to be edited if the user had permission to edit them but will not be able to override any permissions configured for the…

Hi Nikita, I can confirm that if you use ScriptRunner for Jira Cloud it would be possible to achieve this requirement. You could achieve this by configuring a Script Listener to run on the Sprint Started event for your project. The script would start of using JQL to search for all issues in the sprint, and we have an…

Hi Anna, I can confirm if you have ScriptRunner installed, then you can achieve this requirement using Workflow conditions. The plugin has some built-in conditions which may help achieve this requirement otherwise, you can write a custom condition to achieve this requirement as mentioned here. Regards, Kristian

Hi IT, Yes, this is possible, and you read full details of how Script Listeners work inside of ScriptRunner here. You will need to write a custom script to get the field values and copy them to another project when the conditions are met. I can confirm we have some examples in the Libray that show how to copy field values…

Hi It, I can confirm if you have scriptRunner installed, then the Copy Field Values built-in script may be a good fit for your use case. I hope this helps. Regards, Kristian

Hi Reeta, I can confirm that if you use ScriptRunner for Jira Cloud you could use an Escalation service to help achieve this requirement. The escalation service would find the issues to link and then run the script to link to that issue on each issue returned in the query. I can confirm the blog here explains in more…

Hi Sai, I don't believe Atlassian publish a maximum limit for workflows. However, they publish a sizing guide here which states that they class a large instance as having between 800 to 1,800 custom fields. I hope this helps. Regards, Kristian

Hi Sai, I don't believe Atlassian publish a maximum limit for workflows. However, they publish a sizing guide here which states that they class a large instance as having between 200 to 600 workflows. I hope this helps. Regards, Kristian

Hi Shaswini, Thank you for your question. I can confirm that it is possible to write scripts that would interact with an external application or system, as long as the external application or system contains a REST API which can be called to interact with it. We have an example in our library script, which you can use as a…

Hi Seifallah, Unfortunately, the Assign button is an action and cannot be modified as mentioned on the community post here. I hope this helps. Regards, Kristian

Hi Kannpitcha , My apologies for this. Please try reaccessing the link. Regards, Kristian

Hi Fawaz, You are welcome, and I am glad we managed to help you to achieve your requirement. Regards, Kristian

Hi Kannpitcha , I can confirm that I have added an example here, which can be run on the Script Console and shows how to search for a user and set them as the reporter when creating an issue. This example can help create the script you require to achieve your requirements. I hope this helps. Regards, Kristian

Hi Kannpitcha, You are welcome and I am glad this helped you to solve your problem :) Regards, Kristian

Hi Sumit, Thank you for your question. If your string is always the same number of characters and you need to add separator characters at certain points, then you could use the Groovy Substring method to take the user Id generated string and generate sub-strings of each group of characters. You could finally join all the…

Hi Kannpitcha, Thank you for your question. I can confirm that to get the account of a user, you can navigate to the URL of <JiraBaseURL>/people/search inside of Jira to find a user's account ID. If you wish to look up the accountId in a script, you can call the Jira Find Users API, which Atlassian provides to find a user.…

Hi Fawaz, I can confirm we have an example script that can be run on the script console that shows how to set a checkbox field here. You will be able to use this script to help write the rest API call neeed to set the checkbox values via a script listener. I hope this helps. Regards, Kristian

Hi Joseph, Thank you for your question. I can confirm that inside ScriptRunner for Jira Cloud, number fields with the key of "com.atlassian.jira.plugin.system.customfieldtypes:float" like you are using are not supported by Behaviours, which is why you cannot hide this field. You can see the field types which are supported…

Hi Matt, I can confirm that the enhanced JQL functions can only be run on the enhanced search page and not in native JQL due to how the JQL functions are run. However, this does not mean you cannot use the query in other functions, as when you save and share the enhanced search filter, a regular Jira filter is created…

Hi Cesar, Thank you for your question. I can confirm currently the setFieldOptions does not exist as Atlassian do not provide this in the UI Modifications API which behaviours is built on. Can you please raise your use case on the feature request we have for this on our Nolt Board so that our product owner can see this and…

Hi Lori, My name is Kristian, and I am a developer from the ScriptRunner for Jira Cloud team. Thank you for raising this issue, I have looked into this and can confirm this issue is caused by the line of your script of. def issueTypeId = issueTypes.find { it.subtask && it.name == issueType }?.id The reason this generates…

Hi Ryan, Thank you for your question. I can confirm that when calling the Edit issue API to update an issue field you can not send a notification by setting the *notifyUsers * flag to false as mentioned in the Atlassian API docs located here. This means you would simply add in the line below into your rest call after the…

Hi Ryan, Thank you for your question. I can confirm that the reason that your code above will not work inside of ScriptRunner for Jira Cloud is due to the fact the code you have provided is fro ScriptRunner for Jira Server and this will not work as Atlassian only provide a rest API in Jira Cloud and do not provide a Java…

Hi Nivine, Looking at your script it looks like it not finding the custom fields as they have not been specified correctly as custom fields in jira are usually returned in a format similar to customfield_1234 . I would advise basing your script on the example in the docs page below: *…