Update from private bug to public one failure
Bug #676417 reported by
Javier Collado
This bug report is a duplicate of:
Bug #443217: Changing a bug's affected project or description doesn't ever finish.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
After bug name was set from a private to public one, the bug name wasn't updated in the web page despite the operation was succesful (as it could be checked by opening the bug page in the new project name). In addition to this, an attempt, for example, to change the status, failed probably because the url of the bug was incorrect (still contained the old project name).
Maybe a good solution for this would be to redirect to the new bug url after project name has been updated.
| affects: | launchpad → launchpad-registry |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in launchpad-registry: | |
| status: | New → Incomplete |
Revision history for this message
| Javier Collado (javier.collado) wrote | #2 |
| summary: |
- Update from private project to public one failure + Update from private bug to public one failure |
| description: | updated |
| affects: | launchpad-registry → malone |
| Changed in malone: | |
| status: | Incomplete → New |
Revision history for this message
| Deryck Hodge (deryck) wrote | #3 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Deryck Hodge (deryck) wrote | #4 |
To post a comment you must log in.
Launchpad does not have private projects. I do not understand the issue. Which project is this?