Reporting for comment import errors should be clearer
Bug #563857 reported by
Graham Binns
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Graham Binns | ||
Bug Description
What happens:
See OOPS-1549SCW7. In that case the comment data being returned by the remote server isn't importable because of an invalid email address. However, the problem is reported on the bug page as "Launchpad couldn't import bug #2409 from Async Bugzilla," which is staggeringly unhelpful.
What should happen:
Comment import errors should have their own statuses in the BugWatchActivit
Related branches
lp:~gmb/launchpad/add-bugwatch-statuses-for-comment-syncing-bug-563857
- Eleanor Berger (community): Approve (code)
-
Diff: 67 lines (+34/-1)3 files modifiedlib/lp/bugs/interfaces/bugwatch.py (+24/-1)
lib/lp/bugs/model/bugwatch.py (+2/-0)
lib/lp/bugs/stories/bugwatches/xx-bugwatch-errors.txt (+8/-0)
| Changed in malone: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Graham Binns (gmb) |
| milestone: | none → 10.04 |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #1 |
| Changed in malone: | |
| status: | In Progress → Fix Committed |
| tags: | added: qa-needstesting |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in malone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in db-stable r9256 <http://