Organization-wide milestones

[zander]

Feature Description

The current scope of a 'milestone' is a single git repo.
When you have multiple repositories that are part of an organization, this can become less useful.
It would be nice if a single milestone could be applied to multiple repositories under the same organization.

A milestone could then be used to identify all the remaining issues for "the next release", which covers multiple repositories.
It would be very useful to list all the issues assigned to this milestone in an organization and not have to go to each repo where this is duplicated.

Additionally, this allows for more scrum-like behavior, as you can then use either projects or milestones as sprints, and the other as epics.

[6543]

partial a dublicate of #13405

[delvh]

Then let's de-duplicate it by focusing this issue only on the unimplemented part, the org-wide milestone part.

[lunny]

I think it's still a proposal but not a feature. We still don't know what we want. How to create a release in the organization UI across multiple repositories? How to create this release based on different repositories with different tags?

[delvh]

The release part is rather meant as "that will be done for all repos individually".
That is completely separate from the issue of org-wide milestones, and simply what many people do in praxis:
Define a global milestone, and once it's closed, release all subcomponents separately but with the same version.

[lunny]

The release part is rather meant as "that will be done for all repos individually". That is completely separate from the issue of org-wide milestones, and simply what many people do in praxis: Define a global milestone, and once it's closed, release all subcomponents separately but with the same version.

Then every repository will display that release? And one repository could delete that release?

[delvh]

We are talking about completely different things.
The important part is the

The release part is rather meant as "that will be done for all repos individually".

That was meant as that's simply how it is used, not as that's how it's supposed to be done.
I don't want any org-wide releases, I want org-wide milestones in this issue.

[zander]

A milestone is not the same thing as a release. They can be related, for sure. But milestones are absolutely going to have usecases that are not related to a specific or even known release.

An issue can be assinged to the milestone "release v3". But an issue can be assigned to the milestone "full testing coverage". Which is completely orthoganol to the release schedule.

So the only thing that this issue asks for is being able to define and manage milestones at the organization level (parent is org), and then have projects automatically show them and allow issues to be assigned to them just like they can be assigned to project-local milestones today.

Naturally visualization of this different datastructure should also give some new opportunities for org-wide features that may be implicit here.

[stuzer05]

So the only thing that this issue asks for is being able to define and manage milestones at the organization level (parent is org), and then have projects automatically show them and allow issues to be assigned to them just like they can be assigned to project-local milestones today.

Then there should be a way to assing an issue to multiple milestones. In this case, project and org