I need to run a Version Workload Report in JIRA against ALL issues in our system that are currently unresolved.
I would like to run a Bulk Update and ADD a 'Fix Version' value to all selected items. That would provide me with a way to run a Version Workload Report.
Presently, some of those issues already have a 'Fix Version' assigned to them - and we do not want to lose that information. A quick test shows me that if I run the 'Bulk Update' and fill in a 'Fix Version' it will OVERWRITE the existing values. That's NOT what I want. I need to some way to Bulk Update and ADD a 'Fix Version'.
Alternatively, I need some way to produce a very similar report to the Version Workload Report, without supplying a 'Fix Version'. Does anyone know of such a report?
I think the only way for you to accomplish this is by excluding the issues you do not want to perform changes to in your search query. You could consider adding something like "AND fixversion not in (insert fix versions here which you do not want to change, comma separated)".
Alternatively, if the issues you want to change all have an empty value for fixed version you could also try to add "AND fixversion = NULL"
Actually, I came to the same conclusion myself :)
Basically, I'm going to:
Not ideal, because it involves a fair bit of manual work - but do-able.
That said, JIRA should really offer both of the following:
i) Ability to Bulk Update and ADD values to a multi-value field.
ii) Ability to run a Version Workload Report against more flexible criteria. For example, instead of specifiying a Fix Version, you should be able to specify a Filter. This would be VERY useful.
Many thanks for your reply.
Jira should not override the fix version (there should at least be an option to overwrite it or add additional). When you're dealing with loads of issues and need to update them, there is no way doing this manually. However in this case, the bulk operation is also completely useless.
We just learned a lesson in a hard way and hopefully we can fix this in the next couple of hours.
An approach we take is by using the script runner, a custom field and a transition. The recipe is as follows:
* Add a new 'version picker' custom field and call it 'add version'
* Add a circular global transition and call it 'add version', the transition has one transition screen containing the 'add version' custom field.
* In the global transition add a script which adds all versions from the 'add version' custom field to the fix version field.
Now you can actually run a bulk transition, select the add version transition, specify which version you want to add and let it run.
Script which does all the work (including removing fix versions) can be found here
(Note that the script itself is running against an older JIRA, so it needs to be updated).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs