Link "find out why" doesn't really help you to

Bug #185851 reported by era
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Joey Stanford

Bug Description

When I marked bug #185366 as Incomplete, the following message was displayed:

"This bug report will be marked for expiration in 59 days if no further activity occurs. (find out why)"

The "find out why" text is a hyperlink to https://help.launchpad.net/BugStatuses which is helpful overall (I wish I had stumbled over it sooner!) but doesn't say anything about expiration of Incomplete bugs. There is a link to https://help.launchpad.net/BugExpiry but arguably, the "find out why" link should link directly there (and there should then be a backlink from BugExpiry to BugStatuses, I guess).

Furthermore, the BugExpiry page says this feature is scheduled to be implemented in the future, but doesn't really exist yet. Is that true? Then why is the message being added? However, I guess it's not really true.

Tags: lp-bugs
Changed in malone:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Joey Stanford (joey) wrote :

I agree.

Changed in malone:
assignee: nobody → rinchen
milestone: none → 1.2.2
status: Confirmed → Triaged
Joey Stanford (joey)
Changed in malone:
status: Triaged → In Progress
Revision history for this message
Joey Stanford (joey) wrote :

In RF 5612

Changed in malone:
status: In Progress → Fix Committed
Changed in malone:
status: Fix Committed → Fix Released
Revision history for this message
era (era) wrote :

> the BugExpiry page says this feature is scheduled to be implemented in the future,
> but doesn't really exist yet. Is that true? Then why is the message being added?
> However, I guess it's not really true.

It seems I don't have edit access to that page (and it's not clear what I need to do to obtain that access). Could somebody who is better in touch with things see about this detail as well? Thanks.

Revision history for this message
Joey Stanford (joey) wrote :

Hi era, I've updated the BugExpiry page with further details. Let me know if that answers your question.

Revision history for this message
era (era) wrote :

Thanks, it's much better now. However, there are still some remnants which I think need to be updated.

> In a future Launchpad release, projects and distributions will have the option of
> manually expiring old, unattended bugs that have the "Incomplete" status.

This looks like residue from the old version which should simply be taken out now.

> Using these, you'll be able to see which bugs would be expiry candidates if the feature were active.

The future tense here is no longer pertinent.
s/would be expiry candidates if the feature were active/are expiry candidates/

Revision history for this message
era (era) wrote :

Also, as indicated above, a link to https://help.launchpad.net/BugStatuses could be useful for reference.

Revision history for this message
Joey Stanford (joey) wrote :

Hi Era,

Added the backlink, thanks for pointing out that I missed that.

The wording about "the future" is actually still valid. This new feature will allow a project owner to expire bugs, rather than the Launchpad Janitor. I tried to clean up the wording as best I could. Normally we wouldn't include items like this but there was another request it seems for this feature so we previously included it on the help wiki to let folks know it was not forgotten.

Revision history for this message
era (era) wrote :

OK, I think I understand. Thanks for your patience (-:

Revision history for this message
Joey Stanford (joey) wrote : Re: [Bug 185851] Re: Link "find out why" doesn't really help you to

Glad to help actually. Thanks for reminding me about the other items here.

On Fri, Feb 22, 2008 at 11:56 AM, era <email address hidden> wrote:
> OK, I think I understand. Thanks for your patience (-:

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.