Kristian Walker _Adaptavist_ Community Champion

Hi Naggappan, Thank you for your response and no problem. I can confirm then you should be able to make the changes as suggested by Dirk above and I can confirm that the warnings you are seeing are just static type checking warnings as documented here and these may not stop the script from running, so I would advise you to…

Hi Nagappan, I can confirm version 8.13.1 is a Jira Server version and your screenshots show your code is from Jira Server. You will only be using Jira Cloud if your instance URL ends in .atlassian.net. Regards, Kristian

Hi Yazon Thank you for your question. I can confirm that with ScriptRunner for Jira Cloud that we provide the Workflow Validators feature as documented here which allow you to define a condition that must be met in order for a transition to be allowed and you will be able to use this feature to mandate the assignee must be…

Hi Glenn, Thank you for your question. I can confirm that unfortunately, ScriptRunner for Jira Cloud does not have the same Send a custom Email post function that the server version has and I can confirm you can see a full list of differences between the cloud and server versions of the plugin inside the documentation page…

Hi Trudy, I can confirm that currently, ScriptRunner for Jira Cloud does not provide the same Issue Picker scripted field option that Script Runner for Jira Server provides. Regards, Kristian

Hi Erika, I am unable to say what order Jira stores the attachments in as this is handled by Jira itself and I would advise raising a support ticket with Atlassian to ask them this question as they should be able to advise on this. Regards, Kristian

Hi Erika, I can confirm if you log out the whole attachment object which in your script is called mappa2 that you will see that each attachment has a property on it called created which shows the date the atatchmnent was created (added to the issue). This means in your code you need to write some logic to get the cretaed…

Hi Laurens, I can confirm that Project Configurator exports the fields by there name and the type and the Jira API's which are used to import the configuration is what assigns the field its ID. If the same ID is available then Jira will reuse this but we cannot always guarantee that this the case and this why we always…

Hi Marco, I can confirm that as Laurens has said above that Project Configurator can be used to migrate projects between instances however, I can confirm that Project Configurator does not officially support the Insight add on so we cannot guarantee if this will be able to migrate the insight data and configuration as…

Hi Fadouha, Please note that I will help as best as I can but I am not an expert on ScriptRunner for Jira Server. However, I can confirm when using Select list fields you need to get the value out of the *List* data structure to compare to in your script and I can confirm we have an example located here which shows how to…

Hi BenK, Thank you for your question I have reviewed your attached error shown above, and can confirm the reason why the issue data cannot be imported is because there is a post function on the *create* transition in the workflow which is failing and the *built-in Jira data import functionality* which *Project…

Hi Jeanne, As mentioned above, the reason is that you cannot run this code as a Scripted Field as I have explained as Scripted Fields cannot run put requests and only update when an issue is reloaded in the browser and not on issue update. Also, I can confirm in your script that you are attempting to make a rest call after…

Hi Jeane, In you script above you just have the return statement of return output and you need to change this to convert the value returned as an integer value by changing the line to be similar to return output as Integer. Also, I can confirm that scripted fields just calculate values on an issue when it is loaded and you…

Hi Jeane, The error message indicates the values are still stored as strings and you cannot perform mathematical operations on Strings. This means you will need to parse the strings to convert them to integer values which are stored as integer values and then you can multiply these integer values in your script. Regards,…

Hi Jeanne, I can confirm if the value returned in your script is a string you can use the parseInt() method that groovy provides to return it as an integer as documented in the groovy docs located here. I hope this helps. Regards, Kristian

Hi Nasim, I am unsure on automation but I would suggest writing a script with ScriptRunner as suggested above as this should be able to solve your requirement. Regards, Kristian

Hi Nasim, Can you please confirm did you try creating this with Automation for Jira or with ScriptRunner for Jira Cloud? Regards, Kristian

Hi Stephane, Thank you for your question. I can confirm that currently that is not possible to make fields read only with ScriptRunner for Jira Cloud as we do not provide the same behaviours functionality that the server version provides. We are looking into adding behaviours in future and have a backlog ticket for this…

Hi Henry, Thank you for your response. I can confirm that you could achieve this requirement using ScriptRunner for Jira Cloud and by writing a script Listener script which is configured to run on the comment created event. The script would then need to check if the comment author matches the assignee of the ticket and if…

Hi Chris, I can confirm that ScriptRunner for Jira Cloud provides the subTasksOf() JQL function which can be used to search for subtasks below an issue that match a certain query and this function may help you to achieve your requriements. Regards, Kristian

Hi Nannete, I can see that you have raised this question inside of our Project Configurator Support portal as well and we will review and answer this on the support ticket that you have raised. Regards, Kristian

Hi Matt, Thank you for your question. Can I please are you running this script as a workflow post function. If so i can confirm the first rest call you have to get the issue will be invalid and this can be removed as postfunctions already have the issue object in the binding so you can simly call issue.fields and then then…

Hi Nasim, I can confirm that if you are using Jira Cloud then currently the Behaviours feature does not exist as we currently don't have this in the cloud version of ScriptRunner but this is something we are looking to add in future as shown in our public backlog here. I can confirm that the Request Type field is what is…

Hi Ben, Thank you for your question. I can confirm that Workflow Conditions inside of ScriptRunner for Jira Cloud are defined using the Jira Expression Framework as documented in the Atlassian API documentation page located here or in the documentation page located here which explains how to add in a new condition to your…

Hi Robin, Thank you for your question. I can confirm that unfortunately, that the Get User Email API which Atlassian provides is an experimental API, which currently is not supported by ScriptRunner for Jira Cloud as currently, we do not support these experimental API's as these change how they work or become deprecated…

Hi Neha, I can confirm the enhanced search add on is not needed. Scriptrynner provides the *enhanced search* page as long as it has been turned on the Settings page which is located in your instance at…

Hi Neha, Thank you for your question. I can confirm that you can only use the ScriptRunner for Jira Cloud functions on the Enhanced Search page as described in the Knowledge Base Article here. Also, I can confirm you can see examples of how to use this query in the cloud version in the documentation page located here. I…

Hi Christian, Thank you for your response. I apologise for the confusion here as ScriptRunner for Jira Cloud has a keyword with the same name and I believe Kate thought you were using the one provided by ScriptRunner which is why she tried to assist by explaining how this works. I apologise for any inconvenience this has…

Hi Christian, Can I please ask when using the IssueLinkType keyword are you using the one provided by ScriptRunner for Jira Cloud as Kate was referring to the keyword that ScriptRunner for Jira Cloud provides and explaining how this works. If you are not using ScriptRunner for Jira Cloud then can you please advise what add…

Hi Esther, Can you please confirm are you running these on the Enhanced Search page inside your instance at the URL of <JiraCloudBaseURL>/plugins/servlet/ac/com.onresolve.jira.groovy.groovyrunner/jql-search-view as the JQL functions can only be run on the Enhanced Search Page in Jira cloud as described here. You can then…