My team has been attempting to use multihoming to provide useful whole-team views of tasks in addition to per-project views. For example, we’ll plan and prioritize items inside a project, and then go to the “parent” project (which multihomes all of our tasks) to plan what the whole team is doing next, across projects.
However, we recently discovered that when you re-order tasks within one project, the relative ordering does not carry through to the “parent” project because each project seems to have its own separate ordering. For us, this removes much of the utility of multihoming.
A couple of solutions to this that I can see include:
- Maintain relative ordering of tasks across all projects they belong to
- Provide a way to filter a project view by the other projects that each task is in. This would allow us to do per-project ordering within the umbrella of another project. This is similar to JIRA’s backlog view, which shows all epics but also allows you to filter by epic, and maintains the logical ordering of tasks when you move them around.