Kristian Walker _Adaptavist_ Community Champion

Hi Elis, I do not another plugin that would provide this JQL function myself but would suggest searching the Atlassian marketplace to see if one exists. Regards, Kristian

Hi Chris, Thank you for your response. I have created a code sample located here based off your code which can be run on the Script Console and shows how you can get the Epic Name value using the Epic Link value off an issue. You will be able to take this code sample and will be able to use it as a reference guide to help…

Hi Elis, Thank you for your question. 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 due to the way that Atlassian restrict how the JQL functions can interact with their infrastructure…

Hi Miller J, I can confirm that it is no longer possible to set a user field using a users name since Atlassian recently updated their API's to make changes to comply with the GDPR legalisation as described here. These changes means that all user references for API's have been updated to use an accountID rather than by…

Hi Musku, Thank you for your comment. I have reviewed your script above and notice that in the issueKey,transitionID, and closedStatus variables that you are have defined your values inside of < and > tags and these tags should be removed as you just need to define your values as plain text inside of the speech marks for…

Hi Jorden, Thank you for sharing this approach for users to be able to follow. Regards, Kristian

Hi Chris, Thank you for your question. I can confirm that the Epic Link field only stores the key for the Epic which the issue is linked to. This means that to get the name of the Epic that you need to make a separate rest call to the Get Epic API provided by Jira Software as described in the documentation page located…

Hi Andrew, Thank you for you question. I can confirm that it is not possible to achieve these requirements out of the box in Jira Cloud as far as I am aware and that to achieve these requriments you would need to use a third party plugin. If this answer has solved your issue can you please accept it in order to mark this…

Hi Shana, Thank you for your question. I can confirm that it is not possible to achieve your requirement of restricting the number of characters in the summary filed with *ScriptRunner for Jira Cloud* due to the fact that that the same *workflow conditions and validators* functions do not exist in ScriptRunner for Jira…

Hi Calum, Thank you for your question. I can confirm that when using Jira Cloud that you can search for issues which use a specific link type by installing ScriptRunner for Jira Cloud and using the JQL Aliases Feature that it provides. Once installed you will then be able to use the IssueLinkType alias to search for issues…

Hi Tushar, I can confirm that we have received the same question from yourself inside of our support portal and that we have answered this question on the support ticket. However to summarise I can confirm that this is not possible inside of ScriptRunner for Jira Cloud due to the fact that Atlassian only provide a rest API…

Hi Tushar, Thank you for your question. I can confirm that we have recieved the same question off of yourself inside of our support portal and have responded on your support ticket. However, I can confirm here that it is not possible to achieve your requirements of returning a list of active/inactive users inside of Jira…

Hi Derek, Thank you for your question. I can confirm that the Create Subtask transition does not have an issueInput parameter in the script context which is why you are receiving the error that you are receiving and that you should change issueInput to be subtask to set the field on the subtask. I have tasted your code…

Hi Jenny, I can confirm that one of my colleagues in the Development team is working on this support request for yourself. Regards, Kristian

Hi Jenny, Thank you for your response. Could I please ask you to raise this bug inside of our support portal located here, so that we can capture more details on this bug which can be shared with the developers. Once we have a support case open for this then we can capture the details about your Jira Cloud instance that…

Hi Jenny, Thank you for your question. I can confirm that the GDPR warning banner will be staying for a short while yet so that we can advise customers who have not yet updated their scripts or to highlight when they add scripts which are not GDPR compliant and need updating. If you have updated all of your scripts then…

Hi Karl-Anders Bringfeldt, Thank you for your question. I can confirm that Project Configurator is only compatible with migrating configuration or complete projects between Jira Server instances. This means that if you wish to migrate configuration or complete projects from a cloud instance then you would need to a copy of…

Hi Dave, Thank you for your question. I can confirm that unfortantetly it is not possible to skip users which no longer exist when running a migration due to the fact that Jira will not allow configuration to be created which is owned by a user who no longer exists. If this answer has solved your issue can you please…

Hi Soumyajit, Thank you for your question. I can confirm that the Project Configurator add on contains a Used By feature as documented here,which will allow you to see a report of how each configuration object is used inside of your Jira instance. I can also confirm that we have a demonstration video outlining how this…

Hi Ashish, I can confirm that it is not possible to achieve your requirement of returning all unused custom fields with ScriptRunner for Jira Cloud as Atlassian do not provide a rest API to obtain this information inside of Jira Cloud. The reason we are unable to provide this functionality is due to the restricted…

Hi Daniel, Thank you for your question. I have created some example code which shows how you can set a custom checkbox field on an issue during from the Script Console which can be viewed here. This code will show you how to set a custom checkbox field and can be used as a reference to help create the post function script…

Hi Narender, Thank you for your question. I can confirm that it is not possible to add in a workflow validator with ScriptRunner for Jira Cloud that can restrict a transition when an epic issue does not have a specific link type. This is due to the fact that the ScriptRunner for Jira Cloud plugin is unable to provide the…

Hi Suchita, Thank you for your response. I can confirm that scheduled Jobs can be scheduled to run on at a set time and to run JQL in your code by calling the Search Rest API provided by Atlassian which is documented here. You can then iterate over each issue provided by the result of the JQL search in order to perform the…

Hi Alex, Thank you for your question. I can confirm that ScriptRunner for Jira Cloud does not provide the same portfolioChildrenOf() and portfolioParentOf() JQL functions that the server version provides in order out of the box in order to search for Portfolio issues as the API to provide this function does not exist in…

Hi Venkat, Thank you for your question. I can confirm that it is possible to return the issues that you want to update via JQL inside of ScriptRunner for Jira Cloud by calling the Search Rest API provided by Atlassian which is documented here. You can then iterate over each issue provided by the result of the JQL search in…

Hi Ash, Thank you for your response. I can confirm that the example script was designed to be created for the Script Console and will need modifying slightly to be used as a Script Listener. You can see what properties are available for the script by clicking the link the Show me link next to the text which says There are…

Hi Suchita, I can confirm that ScriptRunner for Jira Cloud is able to execute code on a scheduled period using the Scheduled Jobs functionality described here. ScriptRunner for Jira Cloud is able to execute rest calls to third-party rest API's and that the simplest way to test executing these calls would be to use the…

Hi Alex, Thankyou for your question. I have answered your question through the support ticket that you submitted inside of our ScriptRunner for Jira Cloud support portal. I have put the answer here for reference which is that the syntax to set the *accountId* must specify *id* as the key inside the *Array* as this what the…

Hi Ash, I can confirm that to copy the labels to all linked issues in Jira Cloud your script would need to perform the steps below. * Get the parent issue object and all of its fields. * Extract the labels from the parent issue. * Extract the linked issues from the parent issue. * Loop over each linked issue. * Make an…

Hi Stephanie, I can confirm that if you are using Jira Cloud that it is not possible to create a Scripted Field like you can do with ScriptRunner for Jira Server. The reason we are unable to provide this functionality is due to the restricted functionality and API's which Atlassian provide inside JIRA Cloud, due to the…