Kristian Walker _Adaptavist_ Community Champion

Hi Paolo, If you have the Adaptavist ScriptRunner for Jira Cloud plugin installed then you can clear the fix version and affects version field for an issue using the example script located here which can be ran from the Script Console. Please note that for this script to work both the Affects Version and Fields version…

Hi Everton, I just wanted to check in and see if ScriptRunner for Jira Cloud was able to help to achieve your requirement here. Thanks Kristian

Hi Sanan, Thank you for your response. I can confirm that the error above indicates that their is a quick filter on the MOCESII DEV board ORIGINAL Scrum Board which has a reference to field called filter which it expects to have a value of Dev Jira. The reason that it is failing is because it cannot find this value as an…

This weekend here in the UK it was so hot that I was able to spend a day at the beach with my partner which was really nice. Long may the heatwave in the UK continue. Kristian

I was fishing for Sea Bream and Mackerel and luckily it was a good session as i managed to catch a few of each.

I spent the 4th July on Brighton Marina here in the UK doing a bit of Fishing and enjoying the heatwave that we have been having in the UK recently. 

Hi Everton, You can achieve your requirement to create a filter of all closed issues which do not have a root cause issue linked to them using the Enhanced Search Page provided by ScriptRunner for Jira Cloud as described here. You will then be be able to create a JQL search using the linkedIssuesOf() JQL function which is…

Hi Shreyas, I have created some example code which shows how you can get the set different user picker fields in a script run from the Script Console which can be viewed here. This code will show you how to set the assignee, reporter and custom user picker fields on an issue and can be used to help you modify your script.…

HI Shriya, The error shows that versions of the plugins are different between the source and the target instance. In order to resolve this error you will need to update the plugins on the source instance to be the same as the target instance. I have indicated below what version each plugin should be on the target instance.…

@Monique vdB- I was on holiday for the first week in July so missed a chance to upload a picture. Can I still earn the July badge with not having uploaded a picture last week?

Hi Mitch, I can confirm that your code is from the ScriptRunner for Jira Server plugin and the Jira Cloud version. The reason for that is that the cloud version can only make changes to Jira via the Atlassian Rest API's as cloud does not have a Java API like the server version does. This is described in more detail in the…

Hi Liran, Thank you for your response. The script is designed to just sum up the story points from all sub tasks and does not check what status a sub task is in. You would either need to update the script to check the status of each sub task and not sum up its value if it is in the Done status or you would need to add a…

Hi Shriya, Thank you for your response. We believe that this error is being caused by a corrupt attachment inside the attachment directory being backed up, and that this attachment is causing your export to fail. To work around this you could take a copy of the source instance without attachments over to a local server to…

Thank you Liran. This is fine and will show people searching for a similar question that the answer is correct. Regards, Kristian

Hi Liran, Thank you for confirming that issue has now been resolved. Could you please mark this answer as accepted so that other users searching for the same question know this is a correct answer. Thanks Kristian

Hi Liran, I can confirm that you can modify the Store Subtask Estimates in Parent issue on Issue events example in the documentation to sum up story points. I have included a link here to a modified version of this example that you can use to do this. Please note that when configuring this example as a Script Listener you…

Hi Mordechai, I have enclosed a sample script which you can run in the Script Console to update an issue and set a single user picker field. def issueKey = '<IssueKeyHere>' def newSummary = 'Updated by a script - Setting User Picker Field' def result = put('/rest/api/2/issue/' + issueKey) .header('Content-Type',…

Hi Shriya, The error inside your screenshot above indicates that the Zip file being imported is corrupted which could of happened during the data transfer from the source instance to the target instance. In order to validate the file could you please check the following. * That the file contains an extension of .zip on the…

Hi Mike, Thank you for your question. I can confirm that ScriptRunner for Jira Cloud is different to ScriptRunner Jira Server as Jira Cloud does not provide the Java API which the server version has as Atlassian restrict what functions can be performed on cloud through the Rest API. This is reason that your Import…

Hi Shriya, Thank you for confirming the solution worked. Can you please mark the answer as accepted so that other users searching for the same question can see that this marked as a valid solution. Regards, Kristian

Hi Shriya, I can confirm that the error shown in the screenshot above indicates that there is already an Issue type of Test inside of the target instance that you are importing into. Issue type names are case sensitive so an issue type with the same name in a different case such as 'test' would be classed by the importer…

Hi Shriya, Thank you for your question. I can confirm that the error message above indicates that an agile board is being exported from the source instance which does not have a filter configured for it, as the filter associated with it has been deleted. The workaround for this issue is to identify the agile board or…

Hi Shira, Thank you for confirming that this issue has been resolved. Kristian

Hi Shira, Can you please post the contents of the description variable so we can see why the JSON encoder is not working for this variable with line breaks. Regards, Kristian

Hi Adam, Thank you for your question. I can confirm that it is not possible to see other users filters in the enhanced search page and edit these due to the architecture of the plugin defining how filters are stored against users. If this answer has solved your issue can you please accept it in order to mark this answer as…

Hi Randy, The components field is an array so to set the value you require, you should use syntax similar to the example show below where you specify the component by its name using a name, value pair. issueInput.fields.components = [[name: '<ComponentNameHere>']] If this answer has solved your issue can you please accept…

Hi Sharon, In order to transition a parent issue from a sub task then there is a built in post function provided by ScriptRunner for Jira Cloud as described here. Can you please look at using this function to see if it resolves your issue. If you are still having issues can you please raise a ticket inside of our support…

Hi Kedar, Thank you for your question. I can confirm that Project Configurator is designed to promote configuration from one instance to another instance such as from a development instance to a production instance. You will find guides on how to export and import the configuration of projects inside the documentation…

Hi Krishna, Thank you for your question. I can confirm that Project Configurator will be able to move all of the configuration only from one instance to another and you can find help guides on how to do this inside of the documentation page located here, along with the page here which lists all of the configuration objects…

Hi Andrew, Thank you for confirming that your issue was resolved. Can you please mark my answer as accepted so that other users with the same issue can easily find this as the correct solution. Thanks Kristian