On Mon, Dec 20, 2010 at 1:02 PM, Igor Vaynberg <[email protected]> wrote: > there are some that are assigned for 1.6 because we are not fixing > them in 1.5. lets not touch those. we need to be able to assign to > future versions. i think we can keep things assigned to 1.5.0 for > things that need to be fixed before the final comes out and reassign > them to milestones as we are fixing them. ie we need to be able to > communicate: > > this issue cannot be fixed in the next minor release - maybe because > it breaks api > this issue cannot be fixed in the next major release - maybe its > outside of scope > this issue is scheduled post next major release - starting to create the > roadmap > > > so i dont think fix versions are bad, what is bad is that people other > then developers can assign them.
Can we: 1 - add a field "target fix version" for the scenarios you describe above and 2 - change it so that only JIRA project admins can assign either field "target fix version" and "fix version" I've never used JIRA much on the admin side, so I am not sure what can be done, but those seem like standard requirements. -- Jeremy Thomerson http://wickettraining.com Need a CMS for Wicket? Use Brix! http://brixcms.org
