makeplane
[feature]: Manage releases
Is there an existing issue for this?
- [X] I have searched the existing issues
Summary
Allow managing version releases independent of cycles
Why should this be worked on?
Some teams don't release a new version at the end of each cycle, but rather plan them differently.
One specific request regarding releases that would make this feature significantly better than Jira's would be the ability for releases to span across projects. A release may include tickets from multiple projects to enable features or fix bugs. This is particularly true if organizations choose to break out projects by team rather than application. Additionally, if a release could function like a Plane ticket (fields plus page functionality, history tracking, and optionally comments), it would be great for auditability.
Some fields to consider:
- Name
- Status
- Owner (optional)
- Reviewer/approver (optional)
- Created by (read only)
- Created at (read only)
- Last modified by (read only)
- Last modified at (read only)
If the page could have an editable template, allowing us to pre-populate the release with content to be filled out, it would ensure anyone releasing is thinking about what we consider important for a release in our organization while also remaining flexible for all users, and simpler to implement for the Plane team.
@omarin-disco @lucianogorza Release vehicle as a feature is on the way. We understand the requirement and in a scaled setup, this is a must have construct for highly effective teams. We have planned this for Q4 2024 and will keep you posted on the progress.
