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?
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
A bug is present in JIRA 4.1 (affects) and will be fixed in JIRA 5 (fix for)
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?
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot