How can i modify the JIRA Agile Version Panel JQL query to be based on a custom field and not fixVersion field?

Noa Vershinin August 19, 2014

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?

3 answers

0 votes
BjoernKruse August 21, 2014

Hi,

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?

Thanks, Björn

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 19, 2014

Code. You will need to hack the core code in the Agile plugin. For a minimal change (which is still going to require quite a bit of development), you'll only be able to hack it to use a "version" type custom field.

0 votes
Noa Vershinin August 19, 2014

BTW, we are working with JIRA Agile v6.5 and JIRA v6.2.7

Suggest an answer

Log in or Sign up to answer