We're using a custom field called plannedVersion for all issue planning purpeses.
The fixVersion field is left empty up untill the point it was actually fixed, and it's beeing filled with the correct value.
In this senario, since the planning panel in the Agile board is based on the fixVersion value, all the filters results are empty.
Is there a way we can modify the version panned JQL query so that it is based on our cutom field?
Also, is there a way we can change the planning board table template so that it will present the plannedVersion field insted of the fixVerion field?
very similar situation here. As you (Nic) state here https://answers.atlassian.com/questions/32172/affects-and-target-version"Fix Version" can be understood in two different ways ("Issue was fixed in Version" or "To be fixed in Version").
With JIRA Agile we are bound to the latter case.
But that field is (imho) usually named "Planned Version" or "Target Version".
As core-coding is not an option for us, we have to
- tell our teams that "Fix Version" actually means "Target Version"
- create a custom field that represents the "Issue was fixed in Version"
- give that field a short descriptive name that distinguishes it from "Fix Version" (any ideas welcome!)
Or am I overlooking something and there are other options for us?
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events