AJAX behaviour is not supported on people and team bug listings
Bug #887232 reported by
Diogo Matsubara
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Aaron Bentley |
Bug Description
When viewing people and team bug listings, none of the ajax functionality is present. The navigation links fetch new pages, and the new sort order widget and "visible information" cog do not show.
To reproduce: visit any person or team bug listings page while logged in as a member of ~launchpad-
There's no sort widget as you can see here: https:/
Related branches
lp:~abentley/launchpad/person-bug-listings
- Brad Crittenden (community): Approve (code)
-
Diff: 342 lines (+121/-44)9 files modifiedlib/lp/app/browser/launchpad.py (+13/-0)
lib/lp/app/browser/tests/test_launchpad.py (+26/-3)
lib/lp/bugs/browser/bugtask.py (+6/-0)
lib/lp/bugs/browser/tests/test_bugtask.py (+14/-2)
lib/lp/bugs/javascript/buglisting.js (+2/-1)
lib/lp/bugs/javascript/tests/test_buglisting.js (+15/-1)
lib/lp/bugs/templates/buglisting-default.pt (+1/-37)
lib/lp/bugs/templates/buglisting-embedded-advanced-search.pt (+3/-0)
lib/lp/bugs/templates/bugtask-macros-tableview.pt (+41/-0)
summary: |
- person's bug page does not show sort widget + Sort ordering and customise visible information widgets do not show on + people and team bug listings |
description: | updated |
summary: |
- Sort ordering and customise visible information widgets do not show on - people and team bug listings + AJAX behaviour is not supported on people and team bug listings |
description: | updated |
Changed in launchpad: | |
assignee: | nobody → Aaron Bentley (abentley) |
status: | Triaged → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm marking this bug as Critical because this feature will not meet the stakeholder requirements until this bug is fixed.