I noticed that when you bulk edit items, if you have items from more than one JIRA project being edited - the Fix/ Version field does not display. I was wondering why that is? In this scenario, all the projects involved use the Fix/Version field.
The field displays when I bulk edit items within the same project.
Thanks.
Versions are local to projects. So you can't set versions cross-project.
Thanks for the response. Nic. I've used JIRA for 5 years and didn't know that... :/
I appreciate the info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's the sort of quirk that makes sense, but you never think about it until you run into it!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Absolutely. I'm actually a little embarrassed I posted the question after seeing your response. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wouldn't be - it took me until version 4 to notice it myself. I started with version 2...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can confirm! Still the case in 2019. Ty for the tip!
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.
Jira doesn't have "cross project versions", so I'm curious as to what you think you were doing there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In our Portfolio Plan View (we're on the hosted plan) I can create cross-project releases which will automatically create a release for each project. I could previously take a mixture of issues within those projects and bulk update the Fix/Version. I had to release each one individually, but I could create them together.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, that's exactly what we did. Each version exists in all projects of category X (thanks ScriptRunner Version Listener!) and Portfolio has the cross-project version.
Yet, bulk edit is too stupid to allow setting either the local project's fix version or the Portfolio cross-project version.
This seems like it would be a fairly common use case...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, this is a fairly common use case. It is annoying that it is necessary to go to each project to do the bulk update. :-(
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.