How to reorder the Affects Version?

[srinivasp]

when an issue is created, the Affect's Version always list the Released Version first followed by the Unreleased Version. It would be better if it lists the Unreleased Version first followed by released Version. How to handle this?

[Colin Goudie · Accepted solution]

Why would it be better? Affects version should really ONLY be used on released versions. The FIX FOR version should be used for released versions.

[srinivasp]

That is actally a user requirement and i dont have any idea about it. In your answer if both are using released versions, what makes difference?

[Colin Goudie]

For scheduling issues etc.. with GreenHopper and many of the built in REPORTS, the version selected will be looking at issues that have that version assigned to their FIX FOR field. It will IGNORE the Affects field.

Much better if your 'user requirements' reflected JIRA's way of doing things as things will work

e.g.

A bug is present in JIRA 4.1 (affects) and will be fixed in JIRA 5 (fix for)

[Devu Heda]

We have a similar issue. Here is the scenario, during release cycles the QA would like to see the Unreleased versions upfront as they are working on an active release (Unreleased).

Is there a VM template or jsp that we could use to modify what gets shown first in the list?

-Thanks