@Mark: yes, for the moment we're linking bugs (or creating new bugs) assigned to ayatana-design to track such tasks. But I'd like to have a more generic mechanism to manage both the flow of tasks/bugs upstream, with a way to have a kanban-style priority list for both design & dx to work on.
The views associated with tags has limits (assignee not shown, no cross-project "joins" afaict), while the milestones view provides that, albeit at the cost of some more management heaviness. I'll review that with the LP folks, but in the meantime, i recommend we continue using 'also affects' -> ayatana-design and use a backlog milestone.
@Mark: yes, for the moment we're linking bugs (or creating new bugs) assigned to ayatana-design to track such tasks. But I'd like to have a more generic mechanism to manage both the flow of tasks/bugs upstream, with a way to have a kanban-style priority list for both design & dx to work on.
The views associated with tags has limits (assignee not shown, no cross-project "joins" afaict), while the milestones view provides that, albeit at the cost of some more management heaviness. I'll review that with the LP folks, but in the meantime, i recommend we continue using 'also affects' -> ayatana-design and use a backlog milestone.