The reporter role can now create, edit, and delete iterations and milestones

Problem

There were no clear criteria for why the decision was made to restrict Milestone CRUD to Developer+ roles (gitlab-foss#32215 (closed)). We've received feedback from several customers along the lines of:

http://about.gitlab.com/blog/2020/11/11/gitlab-for-agile-portfolio-planning-project-management/
http://docs.gitlab.com/ee/user/permissions.html

Link 1 talks about using Milestones at the higher-level groups for quarterly planning. However, link 2 says that only the Developer access-right can create milestones.

Now if we grant the Developer access-right at a high-level in the group-structure, I think their access-rights will cascade to all of the sub-groups and projects underneath. This isn’t something we’re allowed to do for control compliance reasons. In fact, we currently have to review and approve Developer access on a per-project basis.

Proposal

• Allow Reporter roles to create, update, or delete Milestones and Iterations

Release Notes

We've changed the permissions necessary to create, edit, and delete milestones and iterations from Developer to Reporter. This update better reflects the typical day-to-day Reporter responsibilities of managing and tracking planning timeboxes.

http://docs.gitlab.com/ee/user/project/milestones/#creating-milestones

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.