Cross Project Milestones

[akitaonrails]

One way to scale projects is to have different teams working on separated projects to maintain focus and efficiency.

But it's difficult for projects to coordinate because you would have to get in and out of different boards to see how they're doing.

Instead we could show all the related projects' Milestones in all the boards.

We should create a new "Portfolio" entity. So:
Team has many Portfolios
Portfolio has many Projects (portfolio_projects many-to-many table, no need for explicit model here)

Then the StoryCollection must be able to fetch the stories of it's project + the milestone stories from the related projects to render in the same board (possibly with a different color, tag, icon or something to clearly illustrate where that milestone came from).

So each project can control their own stories and the other projects can immediate visualize if they will be able to deliver their stories until the "global" milestone.

Milestones have static dates, so they should appear in the same position in all the backlogs.

We could add a field to the stories table, so if it is a milestone and if it has the global flag, all projects must show them.

In the View the global milestone must show the project name to differentiate from local milestones.

[andrerpbts]

Based in our conversation (@akitaonrails and @adbatista), it was defined to follow this implementation:

• Projects will have a new field, to store a string tag name, which will group all projects which belongs to the same tag. This will be clear in project list page, for example, where projects will appear in order of grouping before it's name order. This field will be maintened in New/Edit Project pages.

• Projects can belong to just one tag by time.

• Once projects are grouped, they will share release stories between them. So, this will make possible to check the milestones in some project by seeing a release story from another project of the same group.

  • If the release story is being viewed in its project board, then it will be possible to edit, move, delete it.
  • Otherwise, if we are seeing a release story which belongs to another project in the group, this will be read-only and will stay fixed in the same position as the original release story is.

[andrerpbts]

This issue is blocked temporarilly, since we need to solve another things related with releases before implement cross projects milestones.