Skip to content

bug-triage: link to launchpad's expiration explanation #280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 6, 2025
Merged

bug-triage: link to launchpad's expiration explanation #280

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/contributors/bug-triage/bug-status.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,7 @@ have any questions, contact the {ref}`bug-squad` via their mailing list.

: When you ask the reporter to provide any necessary information in a comment,
subscribe yourself to the report so you will get any updates to it via e-mail.
If anyone (including yourself) comments on it, the 60-day expiration clock is
reset.
A bug without assignee or milestone will [expire after 60-days](https://documentation.ubuntu.com/launchpad/user/reference/bugs/bug-expiry/), unless anyone comments on it.
Copy link
Collaborator

@rkratky rkratky Nov 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A bug without assignee or milestone will [expire after 60-days](https://documentation.ubuntu.com/launchpad/user/reference/bugs/bug-expiry/), unless anyone comments on it.
A bug without an assignee or milestone {external+launchpad:ref}`expires after 60-days <bug-expiry>`, unless someone comments on it.


: For more on this, see {ref}`bug-responses`.

Expand Down