OOPS IDs should be shown in the bug watch activity log
Bug #564686 reported by
Graham Binns
on 2010-04-16
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Launchpad itself |
High
|
Graham Binns | ||
Bug Description
At the moment OOPS IDs for BugWatchActivity entries aren't shown in the BugWatch activity log on BugWatch +edit. They should be, since we otherwise need to find them by doing DB queries.
Related branches
lp:~gmb/launchpad/show-oops-ids-bug-564686
- Aaron Bentley (community): Approve on 2010-05-17
-
Diff: 221 lines (+95/-9)6 files modifiedlib/canonical/launchpad/webapp/tales.py (+12/-0)
lib/canonical/launchpad/webapp/tests/test_tales.py (+41/-0)
lib/lp/bugs/browser/bugwatch.py (+2/-0)
lib/lp/bugs/browser/tests/bugwatch-views.txt (+3/-0)
lib/lp/bugs/stories/bugwatches/xx-edit-bugwatch.txt (+34/-9)
lib/lp/bugs/templates/bugwatch-portlet-activity.pt (+3/-0)
| Stuart Bishop (stub) wrote : | #1 |
| Graham Binns (gmb) wrote : Re: [Bug 564686] Re: OOPS IDs should be shown in the bug watch activity log | #2 |
On Fri, Apr 16, 2010 at 02:07:06PM -0000, Stuart Bishop wrote:
> You might need to make the OOPS pruner aware of these OOPS ids too.
> Otherwise, they might disappear after a while.
>
Good point. I'll file a bug.
Graham Binns (gmb)
on 2010-05-17
| Changed in malone: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Graham Binns (gmb) |
| milestone: | none → 10.05 |
Fixed in stable r10880 <http://
| Changed in malone: | |
| status: | In Progress → Fix Committed |
| tags: | added: qa-needstesting |
Graham Binns (gmb)
on 2010-05-19
| tags: |
added: qa-ok removed: qa-needstesting |
Curtis Hovey (sinzui)
on 2010-06-02
| Changed in malone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
You might need to make the OOPS pruner aware of these OOPS ids too. Otherwise, they might disappear after a while.