This will allow teams to aggerate their launchpad bugs in trello.
And/or even sync the comments to/from launchpad bug to/from trello card via a powerup.
The column name can be used for status, but I do admit the status of the trello bug status most of the time will be unknown. For example, many trello boards have column name "Done" for ~= Fix Released status.
However, the major benefit is the clickable link to the trello card to open the relevant board - e.g. the public Ubuntu Desktop Team board. Or a private Foundations Team board. Such that one can observe the status and progress / kanban view of where this particular bug/card fits in.
The way I see it, is that e.g. Kernel, Foundations, Desktop register remote trackers of trello type. And then e.g. there might be a bug that has 3 trello cards, and multiple packages affected, and one can go from LP -> trello boards to view where the status of a given bug fits within each teams board.
This will allow teams to aggerate their launchpad bugs in trello.
And/or even sync the comments to/from launchpad bug to/from trello card via a powerup.
The column name can be used for status, but I do admit the status of the trello bug status most of the time will be unknown. For example, many trello boards have column name "Done" for ~= Fix Released status.
However, the major benefit is the clickable link to the trello card to open the relevant board - e.g. the public Ubuntu Desktop Team board. Or a private Foundations Team board. Such that one can observe the status and progress / kanban view of where this particular bug/card fits in.
The way I see it, is that e.g. Kernel, Foundations, Desktop register remote trackers of trello type. And then e.g. there might be a bug that has 3 trello cards, and multiple packages affected, and one can go from LP -> trello boards to view where the status of a given bug fits within each teams board.