Feature #1360
closed
Permission for adding an issue to a version.
0%
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
Updated by
Updated by Curtis Stewart over 16 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????
Updated by Jean-Philippe Lang about 15 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.
Updated by Jean-Philippe Lang over 12 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.