Bug watch URL's use global sequence number (per-bug sequence is desired)
Bug #98639 reported by
Mark Shuttleworth
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Ensuring that there is a canonical_url for a bugwatch uncovered this
issue. A BugWatch does not have a per-bug sequence number, and so
the only way to refer to it is via it's ID.
It would be easier, since there is no per-bug sequence for a BugWatch
and we have to leak the BugWatch.id anyway, to hang bugwatches off a
global /bugwatchs/nnnn
However, we want in future to have them at /bugs/nnn/+watch/p where p
is not the BugWatch.id but instead a per-bug sequence number (1, 2,
3...) for the 1st, 2nd and 3rd watches added for this bug,
respectively. So we are going ahead and hanging this off the bug to
which it belongs as a first step towards getting the basic URL schema
correct.
| Changed in malone: | |
| assignee: | nobody → bjornt |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
| Changed in malone: | |
| assignee: | Björn Tillenius (bjornt) → nobody |
| visibility: | private → public |
| summary: |
- Bug watch URL's leak their ID's + Bug watch URL's use global sequence number (per-bug sequence is desired) |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| Changed in launchpad: | |
| importance: | Medium → Low |
To post a comment you must log in.
Just sorting out some bug priorities - this isn't currently scheduled, which means Low per our current guidelines.