Link the stages in cycle analytics according to how customers work

Problem to solve

Ex: Teams might and should use multiple MRs to work on the same issue, so we should incorporate the information of all related MRs when we look at a cycle time of a particular issue. Do we expose linking through the stages or we make it implicit by just allowing users to select the right event, i.e. issue mentioned in an MR description or subject or a commit subject; https://gitlab.com/gitlab-org/gitlab-ce/issues/45298

Intended users

Further details

Proposal

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

Edited Sep 05, 2019 by Virjinia Alexieva
Assignee Loading
Time tracking Loading