Feature #1360

Permission for adding an issue to a version.

Added by Curtis Stewart over 9 years ago. Updated over 5 years ago.

Status:ClosedStart date:2008-06-03
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues permissions
Target version:2.1.0
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 versions Closed 2008-05-16
Related to Redmine - Feature #1919: Separate permissions for changing assigned-to, % finished... Closed 2008-09-18
Related to Redmine - Feature #9421: Prevent attribute changes once an issue is assigned to a ... Closed 2011-10-13
Duplicated by Redmine - Feature #7694: Require permission to assign a version to an issue Closed 2011-02-23

History

#1 Updated by Thomas Lecavelier over 9 years ago

Duplicated from #1245

#2 Updated by Curtis Stewart over 9 years ago

I did not realise that this was a duplication. I did a search for issues "all words" for
"version status" and the issue did not show up.
I just redid the search with "status version" and both issues show up????

#3 Updated by Jean-Philippe Lang about 8 years ago

  • Category set to Issues permissions

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.

This is committed in r3020. But I keep this ticket open since the original request was for controling version assignement based on user's role.

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

  • Status changed from New to Closed
  • Target version set to 2.1.0
  • Resolution set to Fixed

Implemented as part of #3521. You can now control the permission on each field per role, tracker and status.

Also available in: Atom PDF