Kristian Walker _Adaptavist_ Community Champion

Hi Slarkin, I can confirm that unfornatetly that ScriptRunner for Jira Cloud does provide the same linkedIssuesOfRemote() JQL function that the server version has and this means that with ScriptRunenr for Jira Cloud then it is ot possible to search for issues with external links. I can confirm that you can see full details…

Hi Des, Thank you for your question. I can confirm that if you want to return the issues within the subtasks as well then you will need to install an add on that provides a search function that can search for subtasks below an issue that macth a specific query. I can confirm that ScriptRunner for Jira can do this and we…

Hi Jibu, Thank you for your response. I can confirm if you do not have both plugins installed then as the page says then you can specify the full URL to your instance in the Rest API call and you can include authorisation to authenticate with Confluence as the API's are different between cloud and server so you cannot use…

Hi Jibu, I can confirm that the example you have linked to will not work as this for Jira Server and the APi's are different between the Cloud and Server versions of ScriptRunner, due to the fact Atlassian only provides a Rest API in Jira Cloud and not a Java API like the sever version contains. This means for ScriptRunner…

HI Georges, I can confirm that thee warnings are just static type checking warnings as described here now that the bindings have been restored. As mentioned in this page the warnings can never be fully removed due to the way which Groovy works in a language and with these warnings, I would always recommend testing the…

Hi Team4All, I can confirm in the cloud we do not have a release number. Can you please share a screenshot showing what static type checking warnings you are still receiving? As mentioned previously, there will always be some static type checking errors where the compiler cannot fully understand the code, and these are…

Hi Vineela, I will tag your response as Server for yourself and you should look to try the suggestions that my colleague Jon has suggested above for Jira Server. Regards, Kristian

Hi Alexy, To return only the relevant fields you would need to change that line to be the fields you require, an example is below which shows how to return the summary and a custom field by its ID. In this query string, you would need to specify the names of all system fields and any custom fields you wish to return.…

Hi Alexy, I can confirm that we impose a timeout limit on scripts of 60 seconds in order to prevent long-running code as described in the documentation page here. This means you will need to split your logic up into multiple scripts if your script is exceeding the 60-second timeout limit. However, I notice from your script…

Hi Steve, The steps above are only valid for ScriptRunner for Jira Cloud. For Jira data centre I would advise looking at the Script Registry which ScriptRunner for Jira Server / Data Center has. Regards, Kristian

Hi Alexy, When using the Search for issues API if you want to return more than 100 issues you will need to use pagination by having multiple search queries which the extra issues. This means for the second query and onwards you would an extra queryString paramater of startAt as documented in the API documentation page…

Hi a841990, Thank you for your question. I can confirm that all of the functions apart from the Enhanced Search page are limited to JIRA Administrators inside of ScriptRunner for Jira Cloud as you can only access them from the Add on's administration page or when editing a workflow which only JIRA administrators can…

Hi Georges, I just wanted to follow up and let you know that our developers have deployed some changes now which should restore the issue binding and resolve these static type checking errors. Regards, Kristian

Hi Vineela, Can I please ask are you using Jira Cloud as you have tagged this request as inside of Jira Cloud atlassian provides no access to the database which means you can not check when data in a database table has changed. If you are using Jira Server or Data Center then the suggestion by John is the approach that you…

Hi Andurdaham, The None option was to shown in your last screenshot. In order to set the value, you will need to use the syntax similar to shown in the example located here which can be run on the script console to show how to set an option value in a select list field. You will be able to take the rest call here and use…

Hi Georges, I can confirm that I have raised your request with my colleagues in the development team at Adaptavist and they are going to look into this warning and see if it can be resolved. Regards, Kristian

Hi Anurdhava, Thank you for your response. This indicates the field is a Single Select List field. From the field, I can confirm it does not have an option configured called None so you cannot configure this to have a value of None unless you However, if you want to clear the field so it has no value set then you can do…

Hi @Team 4all and Georges, I can confirm that these errors are static type check warnings as described in the documentation page here and these occur when the compiler does not fully understand the code but these will not the scripts from running. Regards, Kristian

Hi Anuradha Can you send go to the page at <JiraCloudBaseURL>/secure/admin/ViewCustomFields.jspa from before you click on the field and to confirm what type it says the field is in the Type column as I will need to know this type in order to advise further as your screenshot does not show the type of the field. Regards,…

Hi Anurdha, Can you please confirm what type is the custom field as without knowing what type then I cannot advise how to clear its value in your script. Regards, Kristian

Hi Leon, Thank you for your question. I can confirm that ScriptRunner for Jira Cloud can allow you to create a custom field using a Script Listener that calculates a value using either a Script Listener as shown here or that calculates a value using a Scripted Field as shown here. Using this you would be able to write a…

Hi Anurdaha, Can you please confirm what type is the field you are trying to set to None and If it is the status field you are trying to change, you cannot change the value of this field to *None* as Jira does not allow this and requires to change status you must transition an issue and you can only transition to an issue…

Hi Prabhuram, Thank you for your question. I can confirm that ScriptRunner for Jira Cloud can help to achieve your requirement of fetching issues basd on inked issues with the linkedIssuesOf() enhanced search function documented here. This page will show examples of how you can use this function to search for issuses based…

Hi Ricardo, I can confirm that ScriptRunner for Jira Cloud uses Groovy so this means you would need to the standard approach in groovy to catch exceptions. This would mean that you write a try/catch statment in your code in order to handle when the operation fails and in the catch statement if it does you could log a…

HI Anurdha, On your screenshot, you are on the enhanced search page and not on the listener's page which is under the site admin pages and you can access using the link I provided earlier or using the steps in the page which Mohamed linked to. Regards, Kristian

Hi Anuradha, I can confirm that you can check Script Listiners inside of your instance at the URL of <JiraCloudBaseURL>/plugins/servlet/ac/com.onresolve.jira.groovy.groovyrunner/script-events-admin?s=com.onresolve.jira.groovy.groovyrunner__script-events-admin As Mohamed has mentioned it is likely that a script here is…

Hi Anushu, I can confirm we have had some issues with our service recently which has caused scripts not to run as expected which can be viewed on Status Page located here and this has likely been the cause of your issues. Regards, Kristian

Hi Suresh, You are welcome and I am glad that your script is now working as expected. Have a wonderful the rest of your day, Kristian

Hi Suresh, Can you please confirm that you saved the script with line 11 uncommented and the As this User box set to the ScriptRunner Add-On User. After this all new events which trigger the listener should then be able to update the field which is not on the screen. If this does not work then can you please provide a…

Hi Anupam, I can confirm that it is possible to achieve your requirement with ScriptRunner for Jira Cloud by creating a Script Listener that is configured on the Issue Updated event. The script for the listener would then be able to get the changelog property which contains details of what fields changed when the issue was…