-
Notifications
You must be signed in to change notification settings - Fork 119
Use access rights to control who can view and edit tags #162
Comments
Added pull request #168 that adds the functionality to have edit permissions per role. Every role can view tags. Note sure if there is a use case to hide the tag list per role. If the role can see the issue, they can see the tags. That would be the same as hiding the title/description/etc of an issue per role, which is not default functionality. |
@danielvijge Thanks for the development. I'm already keen on trying it out :-) Regarding the use-case for "no viewing permission" for tags: To me this is the same as the access control for all kinds of fields of an issue. For example, we have some custom fields (like affected component) on the issue that are only visible to developers and also some standard fields (like estimated effort) that are not visible to just anyone. The way we use tags is that they are for the development team and they can contain info that is not appropriate for the general audience. That was my original reason for specifying both read and write permissions. |
That would require a bit of more work:
|
Having control about who can edit tags would be a great step forward for us already. When can we expect the feature to appear in the releases? |
See my comment at #168 (comment). There is a working implementation. It needs to be reviewed and tested, and a unit test needs to be written before it can be included in the main release. At the moment I don't have much time, so any help with that would be appreciated. |
For our use-case, it would be great to have access rights that allow to specify whether a specific role can
This way, we could allow developers to edit tags and all signed-in users to view tags, while anonymous users for example can’t see tags.
The text was updated successfully, but these errors were encountered: