We never in the past did this since it affects the release overview making it not list the latest releases nor can you open bugs against such releases (i.e. "affects version" won't work).

Thus using "Archive" is not the right thing to do (blame Atlassian for this :)

What we did do in the past is once the GA/final is out we archive the alpha/beta's of those release that are no longer "relevant" (i.e. beyond 2 major releases back).

You should be able to see that pattern in the "Manage Versions" tab.

Thus I have reverted the "bad" versions archives I could find and went back and archived older versions to at least clean up the version combo list.

About the issue of "accidentally assign things to 9.0.0 fix versions" - that is one of the things jiralint checks
for (https://github.com/maxandersen/jiralint/blob/master/reports-weekly.json#L27) so this should show up if it
ever happens.

/max

Thanks Nick!

On 12/18/2015 02:49 PM, Nick Boldt wrote:

I've archived some of our old, completed releases in JIRA so that
people are less likely to accidentally assign things to 9.0.0
fixversions when they mean 9.1.0.

Context: https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

If you have objections to this or find it prevents you from doing
something you need to w/ JIRA, let me know and I can revert the
change.

Have a good weekend!


jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev

/max
http://about.me/maxandersen