Vote #63340: Permission for adding an issue to a version. - redmineorg-copy202205 - Redmine

編集操作

リンクをコピー

Vote #63340

完了

Permission for adding an issue to a version.

Admin Redmine さんが3年以上前に追加. 3年以上前に更新.

ステータス:

Closed

優先度:

通常

担当者:

カテゴリ:

Issues permissions_23

対象バージョン:

2.1.0_47

開始日:

2008/06/03

期日:

進捗率:

予定工数:

Redmineorg_URL:

https://www.redmine.org/issues/1360

category_id:

version_id:

issue_org_id:

1360

author_id:

307

assigned_to_id:

comments:

status_id:

tracker_id:

plus1:

affected_version:

closed_on:

affected_version_id:

ステータス-->[Closed]

引用

説明

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.

journals

Duplicated from #1245
--------------------------------------------------------------------------------
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????

--------------------------------------------------------------------------------
> 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.
--------------------------------------------------------------------------------
Implemented as part of #3521. You can now control the permission on each field per role, tracker and status.
--------------------------------------------------------------------------------

related_issues

relates,Closed,1245,close versions
relates,Closed,1919,Separate permissions for changing assigned-to, % finished and target version
relates,Closed,9421,Prevent attribute changes once an issue is assigned to a closed version
duplicates,Closed,7694,Require permission to assign a version to an issue