Altering bug report with subscribed private team : The following errors were encountered: (,'displayname','launchpad.View')
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Deryck Hodge |
Bug Description
I've now received two separate reports of this (persistent) error from two separate employees of one of Canonical's contractors trying to use the Launchpad bug tracker to work on the 'ubuntu-
https:/
https:/
and where the submission error dialogue appears, it occurs persistently—for those users. The dialogue is presented on adjustment of Milestones and the like, causing those updates to fail in addition to comment submissions. When I tried to replicate the error (in both cases), the submission "worked for me", as can be seen by comments or adjustments made to each bug report on those occasions.
Ideally Launchpad should quietly degrade to non-AJAX mode if an error has prevented submission and therefore the prospect of data-loss has occurred. It would be preferable to displaying an error message that is unfamiliar to the user or does not give them guidance on what action to take.
Related branches
- Abel Deuring (community): Approve (code)
-
Diff: 87 lines (+50/-2)2 files modifiedlib/lp/bugs/model/bug.py (+7/-2)
lib/lp/bugs/tests/test_bug.py (+43/-0)
description: | updated |
summary: |
- The following errors were encountered: (,'displayname','launchpad.View') + Altering bug report with private team subscribed gives: The following + errors were encountered: (,'displayname','launchpad.View') |
summary: |
- Altering bug report with private team subscribed gives: The following - errors were encountered: (,'displayname','launchpad.View') + Altering bug report with subscribed private team : The following errors + were encountered: (,'displayname','launchpad.View') |
Changed in malone: | |
status: | Fix Committed → Fix Released |
Screenshot from previous independent report received from Malcolm (subscribed) on 2010-08-20.