Users should only be able to create and edit Bugs

Inger Persson February 16, 2024

Hi

I'm in the need to create a role in my project for users that only should be able to create and edit Bugs. The can read everything else but should not be able to create or edit other issue types or do anything else in the project.

It will be used for internal customers that we deliver to so they can report bugs after releases and the reason why I don't want them to have any more permissions is that I don't want them poking around in the project and making a mess 😊

Right now I've added a role and set up a Permission Scheme for my project but there you can only set it up for all issue types and not a specific one. The role is called DAT Kund (swedish)

image.png

Any ideas on if and how I can solve this?

3 answers

1 vote
Kristian Walker _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 19, 2024

Hi Inger,

I can confirm that the Behaviours feature provided by ScriptRunner for Jira Cloud can help to achieve your requirements.

You would create a new behaviour mapped to the Create View and the Bug Issue Type to achieve this.

You would then write a script that would check if the current user was in a member of the specific project role.

If they were, you would then set the issue types to be displayed, which would include Bug, and if they were not, you would set the issue types to be displayed, which would not include Bug.

I can confirm the example script here shows how to check if a user is a member of a project role, and the example here shows how to set the issue types.

These examples will help act as a reference guide to help you create the required script.

I hope this information helps.

Regards,

Kristian

1 vote
Rebekka Heilmann _viadee_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 16, 2024

Hi @Inger Persson 

with Standard Jira this isn't possible. Permissions can only be based on projects but not on Issue Types within.

You can achieve that with ScriptRunner behaviours though: Restricting Issue Types with ScriptRunner for Jira (adaptavist.com)

Kristian Walker _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 19, 2024

Hi Rebekka,

This solution you have linked to is for Jira Server / Data Center and will not work in Jira Cloud as behaviours in Jira Cloud use Typescript and the UI Modifications API from Atlassian.

Regards,

Kristian

0 votes
Dexter de Vera
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2024

Hi @Inger Persson ,

You can use issue security scheme to hide the other issuetype tickets to your internal customer.

Link how to create security level: https://support.atlassian.com/jira-service-management-cloud/docs/create-security-levels-for-issues/

Rebekka Heilmann _viadee_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 17, 2024

Issue Level Security only works once the issue is created and doesn't stop anyone from creating an issue regardless the type.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events