Disable Release edit for Simple Users

[Stefano Astuti]

Disable, based on the user's project role, the ability to modify versions. Currently, a "simple" user cannot create new versions, which is fine, but they can enter a version and add existing tickets. I do not want a simple user to be able to do this. I'm working on company-managed projects.

Overview: I have two Kanban projects managed by the company, one for application development and the other for customer support. In the application development project, I have enabled release management. Currently, a customer support user can access the development project and can only view the tickets; they cannot create, modify, or transition them. I need to give visibility to the development issues because a support agent might need to know the status of their bug report. Up to this point, I have managed to do everything by assigning the support user a project role with limited permissions. Now, I need to allow the support user to see the content of the releases that are about to be released or have already been released, but without being able to modify the issues that are part of that release.

[Jack Brickey]

Hi @Stefano Astuti , are you wanting to restrict the ability to edit the Fix Versions field?

[Stefano Astuti]

No, I want the user to be unable to add or remove issues from the release as shown in the attached image. I want a simple user to only view the ticket list.

[Jack Brickey]

Yes but the fix versions field is what is used to associate a work item (issue) to a release.

Natively you're unable to restrict fields. However, there are possible workarounds if you are using a CMP. You could consider removing the fix version from the edit screen. You may currently only have a single screen for create edit and view and if that's the case, you would need to create a separate screen for the edit. Then you could modify your workflow by adding a transition that would be restricted to a certain group of people, and would present a screen to update the fix version. I realize this is rather ugly and not sure I would go to the trouble of doing it myself but I have seen others within the community going down this path. To that end, you might search the community for similar posts as you might find more compelling answers.

[Stefano Astuti]

Let me give you an overview: I have two Kanban projects managed by the company, one for application development and the other for customer support. In the application development project, I have enabled release management. Currently, a customer support user can access the development project and can only view the tickets; they cannot create, modify, or transition them. I need to give visibility to the development issues because a support agent might need to know the status of their bug report. Up to this point, I have managed to do everything by assigning the support user a project role with limited permissions. Now, I need to allow the support user to see the content of the releases that are about to be released or have already been released, but without being able to modify the issues that are part of that release.