Provide a way to lock/freeze the Feature Board and Releases so only the Product Owner can change them?

It would be helpful if there was a way to lock/freeze the Feature Board and and at least the Release Content so only the Product Owner can change it.  Our Platform has very granular Role specifications for example

  • Bill Dykas
  • Mar 2 2017
  • Already exists
Release time frame
  • Attach files
  • Admin
    Austin Merritt commented
    March 17, 2017 14:48

    This is currently handled using the Reviewer and Viewer roles which allow users to view the Feature board but not edit it. Do you have a use case where you need users to have contributor access (ie but able to edit the features themselves) but not change the priority or move them between releases? If so, can you share more about that to help us understand it? I am going to set this to Already exists for now but we can update it if needed once we understand the need better.

  • Bill Dykas commented
    March 21, 2017 22:02

    Yes.  The goal would be to edit the features but not change priority or move them between releases

  • John Roberts commented
    July 11, 2017 16:51

    I would like to see something like this as well though in a slightly less granular way.  My use case would be to lock a release, and its associated features, from edit of any item in it for roles below Product Owner by a predefined date.  Our development team does not work from Aha but JIRA and once they commit to the features, and have copied them to JIRA via integration, there should no longer be any edits allowed from contributors.  Unfortunately telling people that a release is locked by a certain date has not worked and while we do audit and track changes it would be appealing if we did not have to go back and "fix" those items post lockdown date.