Kristian Walker _Adaptavist_ Community Champion

Hi Rajeev, Can I please ask you to provide the screenshot of how your Post Function has been configured on the Create Transition of the workflow. I can confirm that in order to access the values inside a post function on the Create Transition that you must order your post function to be the last one in the list below the…

Hi Rajeev, From your error trace above I see the message of Condition didn't eval to true, exiting, This message indicates that your script did not run as you have a condition configured for it which did not pass. So that I can advise further on this issue, can I please ask if you can attach a full-page screenshot showing…

Hi Rajeev, Thank you for confirming that our response allowed you to achieve your requirements. Regards, Kristian

Hi Adam, Thank you for confirming that our response has helped you to resolve your issue. Regards, Kristian

Hi Nick, Thank you for confirming this and for confirming that your issue has been resolved. Regards, Kristian

Hi Adam, I believe that the error is coming from the fact that the syntax in your rest call is invalid. I can confirm that we have an example of how to call the notify API with ScriptRunner for Jira Cloud inside of the documentation page located here and I would advise you refactor your script to use the syntax shown in…

Hi Aira, 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 for 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 Ruben. I can confirm that we have now released some documentation for the conditions and validators features which you can find as child pages below the page in the documentation here. I hope this helps. Thanks, Kristian

Hi Nick, Thank you for confirming that the example which we have provided you have resolved your issue and has allowed you to resolve your issues I notice that page is from the Jira Service Desk rest API's and is only relevant to Jira Service desk and is not valid for Jira Core or Jira Server projects which are example is…

Hi Nick, Thank you for your question. I can confirm that we have an example snippet located here which shows how to set different type of user picker fields with ScriptRunner for Jira Cloud. Inside this snippet, we show how to set a multi-user picker custom field which requires you to pass an array for each user to be set…

Hi Alex, Thank you for your question. I can confirm in ScriptRunner for Jira Cloud that you can call the Issue API which is documented in the Atlassian documentation page located here with a Get request. Calling this API will return the JSON for all fields on the issue and one of the fields inside of the JSON will be the…

Hi Rajeev, Thank you for your question. I can confirm the example shown in the ScriptRunner for Jira Cloud documentation site located here shows how to return all of the custom fields in a post function in the customFields rest call located at the top of the script. This rest API call gets all of the custom field objects…

Hi Ruben, I can confirm that Conditions and Validators are development features inside of ScriptRunner for Jira Cloud currently which means we are still working on the full set of features for them. This means that we will have documentation coming out for these shortly and plan to add the ability to test expressions in…

Hi Ruben, hank you for your question. I can confirm that validators in ScriptRunner for Jira Cloud use the Jira Expression Framework as described in the Atlassian documentation here which means you cannot write normal groovy code to write the validator expression. We have created the Knowledge Base article located here…

Hi Denish, Thank you for confirming that your issue has been resolved. To see only comments in 2016 you would need to adjust the query to be similar to lastCommentedDate >= startOfYear(-4) AND lastCommentedDate <= endOfYear(-4) as this joins 2 queries together to search for issues between the beginning and end of the year…

Hi Denissh, Thank you for your question. Can I please ask you to navigate to the page located at <JiraBaseURL>/plugins/servlet/ac/com.onresolve.jira.groovy.groovyrunner/jql-sync?s=com.onresolve.jira.groovy.groovyrunner__jql-sync check if it says any issues need syncing. If any issues show as needing syncing then you can do…

Hi Deva, I can confirm that Atlassian provides the Notify rest API which can be used to send an email and is documented here. Using this API you could look to send an email notification. I can confirm that the example located here provides an example of how to call the Notify API and will be a useful reference guide to…

Hi Deva, I can confirm with ScriptRunner for Jira Cloud that it is not possible to pop up an alert or dialogue box due to the fact that Atlassian does not provide do not provide any Rest API's to display a dialogue. This means that achieving your requirement of popping up a dialogue when the SLA is about to breach will not…

Hi Nick, I can confirm as per the support ticket that you have raised that we have checked this message around the issue security scheme and can confirm that once you have granted Edit issue access to the add on the user then you can ignore this warning as the issues will be synchronised. Regards, Kristian

Hi Cesar, Thank you for your question. I can confirm that you could achieve your requirement with the ScriptRunner for Jira Cloud plugin by creating a Script Listener. The listener would need to be configured to fire on the Issue Created event and its script would need to check if the issue is the issue you require to…

Hi Nick, Thank you for your question. Can you please ensure that the ScriptRunner add on user has full browse and edit permissions inside of the standard project permission scheme as well as the issue security scheme to see if this resolves the error. If you are still encountering issues after trying this workaround then…

Hi Jason, Thank you for your question. I can confirm that ScriptRunner for Jira Cloud is only able to make calls to the Rest API's which Atlassian provides inside of the Jira Cloud Rest API documentation page located here. I have looked at this API and can see that there is no API to call Crowd directly but that they do…

Hi Vando, You are welcome. Regards, Kristian

Hi Michael, I can confirm currently we do not provide any ability to save scripts as a built-in script currently. This means we would advise saving the script somewhere such as a Git repository and then to copy the code from here into the Script Console page each time you wish to run the script. Regards, Kristian

Hi Michael, I can confirm that the example linked above will not work on Jira Cloud due to the fact that the code provided inside of it is for 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 API in the cloud-like they do in Jira Server.…

Hi Vando, Thank you for your question. I can confirm that validators in ScriptRunner for Jira Cloud use the Jira Expression Framework as described in the Atlassian documentation here which means you cannot write normal groovy code to write the validator expression. We have created the Knowledge Base article located here…

Hi Michael, Thank you for your response. I can confirm that it is possible to get the Change History for an issue by making a call to the Get Changelogs Rest API which Atlassian provides and is documented here. Using this API you will be able to return the Change History from an Issue and you will be then able to write…

Hi Michael, Thank you for your question. I have checked your requirement and can confirm it is not possible to use ScriptRunner for Jira Cloud to track the details of when a ticket is moved between issues and to post this information on an issue when it is moved. The reason for this is that Atlassian does not provide a…

Hi Ricardo, I can confirm that you set the Time to resolution SLA field on a software project as the SLA fields are only permitted by Jira to used in Jira Service Desk Projects. However, in your script, once you have extracted the value if you save it to a variable in your script as a String then you could set this value…

Hi Ricardo, Thank you for confirming your issue has been resolved. Regards, Kristiaan