Feature #7694

Require permission to assign a version to an issue

Added by Keith Cirkel over 6 years ago. Updated over 5 years ago.

Status:ClosedStart date:2011-02-23
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Permissions and roles
Target version:-
Resolution:Duplicate

Description

We often have multiple version open during our project process - so we can plan features for time periods ahead. Unfortunately some of the people involved in the project constantly assign issues to the wrong versions.

Currently we lock all versions, until the PMs go in and unlock them so they can assign bugs to a version number - obviously this isn't very productive.

I propose a Permission entry in the Permissions and Roles to "Assign Issue to Version", which when unchecked, disallows that role to assign a version to the issue, through updates or creating a new issue.


Related issues

Related to Redmine - Defect #7729: User with only issue view and add note ermission can chan... Closed 2011-02-26
Related to Redmine - Feature #9421: Prevent attribute changes once an issue is assigned to a ... Closed 2011-10-13
Duplicates Redmine - Feature #1360: Permission for adding an issue to a version. Closed 2008-06-03

History

#1 Updated by Jean-Philippe Lang over 5 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Same as #1360 implemented for 2.1.0.

Also available in: Atom PDF