I know this one is really old, but I just came up with a workaround since this is still not possible in 6.3.x and possibly later. Assuming that all issues in query are in the "Closed" status:
You may need to make adjustments to this depending on how many statuses and workflows are involved.
Tested succesfully on JIRA 7.0.0. Thank you !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yup. The workflow loop works perfectly. Just allowed "Allow all statuses to transition into..." my "Done" status and could transition issues with updating the resolution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use the script runner plugin which has a built-in script to bulk change resolutions:
https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts
Cheers Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
We have released Bulk Operation Enhancer For Jira plug-in in marketplace.
https://marketplace.atlassian.com/plugins/com.kostebekteknoloji.plugins.jira.jira-bulk-operation-exhancer
You could do bulk operations like additive adding, replacing and removing labels.
You could also set Resolution field with Bulk Operations.
Documentation is here: http://www.confluence.kostebekteknoloji.com/display/PLUG/Bulk+Operation+Enhancer++for+JIRA
You can also contact with info@kostebekteknoloji.com for your new bulk operation suggestions
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This plugin does the job, when you need to fix current Resolution field value.
But if issue resolution is empty, bulk set Resolution action forgets to set technical "resolution date" which has impact on reports (standard, from apps or custom...)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is it there on the screen for all selected issues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
for individual issue yes, but on bulk screen there is no Resolution field.
Where could be gone :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
another way, check the following document to bulk edit resolutions
https://confluence.atlassian.com/display/JIRAKB/HowTo%3A+Bulk+Edit+Resolution
some one already raised an issue with atlassian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can do this but only if you add the resolution field on to the screen. Add the field to "Edit" screen, bulk "Edit" to change the value and then remove it from screen to avoid people making changes accidently.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We do have "Resolution" field on the Edit Screen but its not showing up for bulk edit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correct - adding Resolution to issue Edit Screen does not solve the problem, bulk edit still doesn't exposes it. But I can edit Resolution on individual issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.