Restricting Access to Specific Columns - Kanban

[Craig McManus]

Hi all,

I'm relatively new to Jira Software and even newer to the Administration of it, so I'm hoping someone can help.

I'm currently running a project using Kanban, where I've got 5 columns for tasks to progress through:

• Backlog
• Ready for Progression
• Returned To Business
• In Test
• Ready for Release

I'm looking for a way of restricting who can see the issues & tasks that are in the Backlog column - only a limited number of people need to see tasks before they are moved to Ready for Progression, when everyone should then be able to see them.

Can anyone offer any guidance on the easiest way to set this up?

Thanks

[Josh Loe]

Craig,

Your board is just a visual of the issues.  There is no way to restrict a specific column which is just the status of the issue.  Your best bet would be to use issue level security:

* https://confluence.atlassian.com/adminjiraserver073/configuring-issue-level-security-861253265.html

-Josh Loe

[Craig McManus]

Hi Josh,

Thanks for the guidance. It looks as though I'll have to find some way to set issues up with issue level security and then, as part of a transition, remove the issue level security.

Thanks again!

[Jack Brickey]

@Craig McManus, Josh's comments are accurate but let me add some additional info that may help. I will first state that this is tedious work and you really need to know you want to go this route.

• As Josh alludes to, columns equate to statuses in your workflow
• So if you want to restrict who can browse issue based upon status then you need to edit your workflow(s) and modify the property of each status that you wish to restrict
• Basically you are going to use property key=jira.permission.browse.group      property value=my group Here is another source that might help - https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status

I would also offer that if you are just trying to declutter things and don't want the backlog on your development board you might consider the following approach:

1. create two boards: one for backlog management/planning and one for the developers (ready for progress...ready for release.
2. the filter for board 1 will include "backlog" or "to do" status whatever represents backlog. I would also recommend including "ready for progression". This allows the planners to move things from Backlog to R4P and remain on the board until they are moved forward
3. the filter for board 2 excludes backlog
4. you can then set the permissions of who can access the boards. Note a user could still see the backlog issues in a JQL query
5. I also note you have a "returned to business" if that means that an issue in development needs to go back to the 'backlog planning team' then you would want the backlog board to include that status

hope this helps rather than confuses. :-)