nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Restricting who can see specific tasks

Alex Chunilal

Hi, I am currently trying Jira Software and have created a workflow for the development team. at the end of the workflow before done, I have 'QA Testing'. This is where the issue has been passed to the testing team to check.

I don't really want the testing team to have access to the product board and also all the other tasks the development team are working on. I only want them to access the 'Issues' that are assigned to them or the testing team project role.

Is this possible to do ?

Accepted answers

John Funk

Hi Alex - Welcome to the Atlassian Community!

You could probably solve this a couple of ways.

1. One is to create a separate board with a filter that only shows issues where the assignee = currentUser()

2. Be sure to share that filter across your organization or with just the project role (or group).

3. Update the product board filter to only share it with those that should see it using a group and/or project role.

4. Or you could implement Issue Level Security with restrictions as needed.
You can learn more about that here: https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html

All comments

John Funk

Hi Alex - Welcome to the Atlassian Community!

You could probably solve this a couple of ways.

1. One is to create a separate board with a filter that only shows issues where the assignee = currentUser()

2. Be sure to share that filter across your organization or with just the project role (or group).

3. Update the product board filter to only share it with those that should see it using a group and/or project role.

Alex Chunilal

Thanks for the quick response. Let me have a check at these options and i'll the your know

Arthur Kennedy Otieno

Hi Alex,

A couple of suggestions:

On the board: Go to Project Setting>People. See if removing people might help
There's also a section on Permissions under Project Settings. Then Click on Actions>Edit Permissions.

Let me know if that helps.

Alex Chunilal

John, thanks. This is what I did

1) I gave the testing team access to the project, but not the actual board.

2) Created a personal board that is filtered on the specific fields that tell me the issue is not ready for testing.

3) I created Issue level security 'High Level' and 'testing' high level has the Admin and the Development project rolls. The 'testing' on has the same but with the addition of the 'testing team' project roll. I set the 'High Level' as the default security

4) I then shared my personal board with the 'testing team' and they have a Kanban board with only topics ready for them to test.

Works a treat.

I have some additional questions as I try an refine the solution.

1) When the testing team get a task, I want them to be able to create sub tasks within for individual issues related to the issue at hand. However. I don't want them to be able to create actual main tasks with in the project, not sure if that is possible

Alex Chunilal

Thanks Arthur but I managed it with what John said

John Funk

Great! Glad you got the first part working!

You might be able to do the last one with some combination of validators on the create transition on the work flow.

The easiest way would be to have different workflows for Sub-tasks (we do that). Then in the workflow(s) for the other issue types just add a validator that the QA Role is not allowed to create those.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

atl-gruland