Project

General

Profile

Actions

Feature #1360

closed

Permission for adding an issue to a version.

Added by Curtis Stewart about 16 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues permissions
Target version:
Start date:
2008-06-03
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

I have several projects with the customers and requesters entering there own requests, bugs, etc. similar to how the Redmine project is organized. I have been using the versions to plan roll-outs and in general that function works great.

I have been having the same problem that I see on this site where the users are adding their issue to whatever target version they wish. I was wondering if there could be a permission added, maybe under issue tracking, like "Can Assign/Modify Version".

The other way would be to add a set of statuses to the version such as "Open", "Locked", and “Completed" where we can specify what actions can be performed on the scope of a version.

Thanks for such a valuable project.


Related issues

Related to Redmine - Feature #1245: close versionsClosedJean-Philippe Lang2008-05-16

Actions
Related to Redmine - Feature #1919: Separate permissions for changing assigned-to, % finished and target versionClosed2008-09-18

Actions
Related to Redmine - Feature #9421: Prevent attribute changes once an issue is assigned to a closed versionClosed2011-10-13

Actions
Has duplicate Redmine - Feature #7694: Require permission to assign a version to an issueClosed2011-02-23

Actions
Actions

Also available in: Atom PDF