Join Malone and Blueprint
Bug #235745 reported by
Andrea Corbellini
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Low
|
Unassigned | ||
Bug Description
Malone and Blueprint allow, respectively, to handle bugs and to draft specifications. Some things which are in Blueprint could be useful for bug reports, like dependency tree and the whiteboard, and other things which are in Malone could be useful for feature specifications, like the ability to send comments, the role of the bug supervisor and the +activity page. Many bugs have been reported to make Blueprint and Malone more similar (like bug #50875, bug #49698, bug #218272, bug #223928), but I think that using the same code, but keeping the two servicies -- specifications and bugs -- separate, would be the best solution.
| description: | updated |
| description: | updated |
| Changed in blueprint: | |
| importance: | Undecided → Wishlist |
| Changed in malone: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Björn Tillenius (bjornt) wrote | #1 |
| Changed in malone: | |
| status: | New → Invalid |
| Changed in blueprint: | |
| status: | New → Invalid |
To post a comment you must log in.
I'm closing this bug report, since it's too vague. This is better tracked as a blueprint, or better, as individual bug reports.