Lock unshipped releases to restrict everyone (including owner & contributor) from editing the release Merged

Idea: Lock unshipped releases to restrict everyone (including owner & contributor) from editing the release

Potential solution: Password lock releases that have finalized scope, timeline, and resources (users can choose when they want to lock the releases)

• Only people with password can unlock the releases to make edits (assuming they received change request for the release)

Alternative: A new permission level where user with the permission can edit releases after releases are locked

Objective: Limit edits of releases that have feature locked down to avoid change scope/timeline during execution of the releases, which resulted in issues on resource allocations

FYI:

• We need this feature because we're using Aha as our primary location to determine product requirement/scope, deadline, and resources

• If confirmed releases are not locked, contributors/owners may

  • Accidentally changed content of the release, which requires additional resource to fix the error

  • Made the changes without confirmation from all parties, resulted in miscommunication and setting wrong expectations for the releases

• I understand shipped releases can not be edited, however shipped releases mean the product is complete and will confuse internal users

Thank you,