Add a "Related releases" section to Issue
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Answer the question: What release of a project references a particular issue I'm looking at.
I am occasionally looking at an issue or merge request and wonder what release of the repo the issue was presumably fixed in or what tag is potentially associated with the merge request/issue?
We try and reference issues in tag release notes and it seems like it would be helpful if similar to the way an issue includes the sections, 1) Linked issues and 2) Related merge requests, how about a new section for 3) Related tags or 4) Related releases.
Intended users
- Rachel (Release Manager)
- Parker (Product Manager)
- Devon (DevOps Engineer) - less work for this person to answer questions about what's in production potentially
- Sidney (Systems Administrator) - to help answer the question of whether a bug fix is potentially in production
- Sam (Security Analyst) - to know what release includes a potential security fix
Further details
When I find an issue that includes a fix for something, I'd like to know what release it went into.
Right now on the Releases page we show the reverse association: all issues and merge requests related to each release. We do this through the milestone association. So if we have a structure like this:
Release
├── Milestone 1
│ ├── Issue 1
│ └── Issue 2
└── Milestone 2
└── Issue 3The release is considered to be "associated" to all three issues. The same applies to MRs.
So I don't think it would be too difficult to reverse this and show the relationship on the issue/MR pages
In fact, we already do something very similar on the milestone list and detail pages:
Some considerations:
- It's possible for the same milestone to be associated to more than 1 release. Because of this, it's also possible for an issue or MR to be associated to more than one release.
- We don't have a way (that I know of) to directly associated an issue/MR to a tag, other than through a release. In my opinion, it doesn't makes sense to show a tag association - only a release association.
Weight estimation
From a frontend perspective, I think this would only take a single MR per page we want to add this info to. So, assuming we would add this to the MR and issue "detail" page (i.e. the individual views, not the list views), this would be frontend-weight2.
I'm guessing the backend effort would be similar - one MR per view. So I'll tentatively set this as backend-weight2 with a total weight of 4. @nicolewilliams, would you mind finding a backend engineer to confirm?
Each page could most likely be developed and released separately (i.e. we could work on adding this info to the issue page separately from the MR page.)
Proposal
Add a section to issues and merge requests for "Related tags" or "Related releases" when issues and merge requests are assigned to milestones that have been associated with a tag/release.
Permissions and Security
Documentation
Availability & Testing
Success would be when I can look at an issue or merge request and quickly answer the question what release did this go into.
What is the type of buyer?
Is this a cross-stage feature?
Yes, this adds changes to the Merge Request and Issue views. Overlapping with devopscreate
Links / references
https://docs.gitlab.com/ee/user/project/releases/#releases-associated-with-milestones