Can't record that a bug was fixed in a now-inactive milestone
Bug #116153 reported by
Matthew Paul Thomas
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
If a bug was fixed in a milestone that has since been marked inactive, that fact cannot be recorded for posterity.
For example, before 1.0, I fixed bug 3790 but forgot to mark it fixed. Then the 1.0 milestone was marked inactive, and removed from the bug report. I tried to re-set the bug to 1.0 while marking it as fixed, but could not.
Perhaps inactive milestones should still be available from the milestone list, but marked "(inactive)" -- and selectable only if the bug is simultaneously, or has already been, marked as Fix Committed or Fix Released.
To post a comment you must log in.
On Tue, May 22, 2007 at 07:24:35AM -0000, Matthew Paul Thomas wrote:
> Public bug reported:
>
> If a bug was fixed in a milestone that has since been marked inactive,
> that fact cannot be recorded for posterity.
>
> For example, before 1.0, I fixed bug 3790 but forgot to mark it fixed.
> Then the 1.0 milestone was marked inactive, and removed from the bug
> report. I tried to re-set the bug to 1.0 while marking it as fixed, but
> could not.
>
> Perhaps inactive milestones should still be available from the milestone
> list, but marked "(inactive)" -- and selectable only if the bug is
> simultaneously, or has already been, marked as Fix Committed or Fix
> Released.
I don't think this is worth fixing. There's already a way of set the bug
to an inactive milestone:
1) activate the milestone
2) set the bug to the milestone
3) inactivate the milestone
Sure, this isn't as easy as it could be, but then it shouldn't be that
common that you want to set a bug to an inactive milestone. If a
milestone has been inactivated, it was probably inactivated for a good
reason, and I can't see why we should add noise to the milestone list
just to address this use case.