Bug 488411 - Mark older version and milestones as inactive
Summary: Mark older version and milestones as inactive
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Bugzilla (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-24 14:37 EST by Marc Khouzam CLA
Modified: 2019-04-12 07:29 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Khouzam CLA 2016-02-24 14:37:20 EST
I was told that there is a way to mark versions and milestones as inactive in bugzilla.  That would allow to keep old bugs pointing to those version/milestones but remove them from the drop down choices.

The dropdown has gotten much too long in CDT so if this option is available, I'd like to mark as inactive:

- all milestones earlier than sortkey 8800 (so earlier than 8.8.0)
- all versions earlier than 8.5

Thanks!
Comment 1 Jonah Graham CLA 2016-02-24 15:12:15 EST
BTW as I was the person who mentioned it on the mailing list I thought I would just make sure I was explicit about what I was referring to.

If you edit the individual version via (I think, but I don't have access)  https://bugs.eclipse.org/bugs/editmilestones.cgi, click on CDT, then an individual version you have the option to uncheck "Enabled For Bugs".

Hopefully there is a way to mass edit them without going through one version at a time.
Comment 2 Eclipse Webmaster CLA 2016-02-26 16:20:37 EST
If you really don't need these I'd recommend we remove them.

-M.
Comment 3 Marc Khouzam CLA 2016-02-26 17:37:21 EST
(In reply to Eclipse Webmaster from comment #2)
> If you really don't need these I'd recommend we remove them.
> 
> -M.

But then what would happen to all the bugs already using those versions/milestones?
Comment 4 Eclipse Genie CLA 2018-02-16 07:47:57 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Jonah Graham CLA 2018-02-16 16:12:57 EST
(In reply to Marc Khouzam from comment #3)
> (In reply to Eclipse Webmaster from comment #2)
> > If you really don't need these I'd recommend we remove them.
> > 
> > -M.
> 
> But then what would happen to all the bugs already using those
> versions/milestones?

Hi, I am trying to pick up some of the work that Marc K used to take on in the releng area, so I'll try and take ownership of this request.

To rephrase the original question, is it possible to remove milestones/versions from being set in the UI, but still preserve that information in old bugs?
Comment 6 Eclipse Webmaster CLA 2019-04-11 09:05:55 EDT
 
> To rephrase the original question, is it possible to remove
> milestones/versions from being set in the UI, but still preserve that
> information in old bugs?

Not really.  We could update the milestones/versions with a text tag like 'obsolete' but people would still be able to file bugs against them.

-M.
Comment 7 Jonah Graham CLA 2019-04-12 07:29:10 EDT
(In reply to Eclipse Webmaster from comment #6)
> Not really.  We could update the milestones/versions with a text tag like
> 'obsolete' but people would still be able to file bugs against them.
> 
> -M.

OK, then this is really a feature request for Bugzilla, so nothing to do with Eclipse for now. Closing.