how to authorize some developers only for a kanban board within the same project?

[Deleted user]

we have a jira instance in our company with a project and a single group. We are not authorized to create new projects or groups at the instance but have the role project lead and admin.
Backlog, epics, user stories and sprints as well as scrum board are all configured and looks good.

If I create a kanban borad based on the instance project all existing user stories are automatically imported/included into the kanban!

Now I would like to create a new empty Kanban board for a new project with several user stories & tasks but no sprints, similar to Continuous Delivery and authorize external developers to only view this kanban and work with its user stories / tasks.

How do I do that? is this possible within the same project instance?

[Avinash Gautam · Accepted solution]

Hi  @[deleted] 

Please create filter for those number of user stories and tasks and share the filter with selected set of users you want. Give a particular name while saving it.

Create a Kanban board. Go --> Configure --> Edit Board filter --> use the filter you have created. This should work as the board will be visible to only selected set of users to whom you have shared the filter.

A Kanban board will never have sprint as sprints are available in Agile boards. Thanks!

--Avinash Gautam

[Deleted user]

Hi @Avinash Gautam 

Thank you for the quick & practical solution.
This solves my problem with the authority to kanban board but how do I create user stories and assign these to epics independently of the existing backlog or outside the backlogs?

[Avinash Gautam]

Hi  @[deleted] 

This is kanban board. Backlog option will not be applicable here.

You can just create user stories, epics, etc(link issues whatever way you like) and mark them with a unique label or a component in the filter. Something like below:

project = XX and issues in (user stories, epic, etc) and component = "xx1" or label = "xx1" order by ASC

Save this filter with particular name and share them with required users. Later

Go Kanban --> Configure --> Column --> first state of the issues(user stories, epics, etc) should be mapped in the first column and accordingly as per your choice.

This will populate all the issues in the kanban directly once they will be created. Thanks!

--Avinash Gautam

[Deleted user]

@Avinash Gautam 

very good workaround solution :-)

the difficulty is that I already have a filled backlog that I use for active sprints. So the challenging task was and still is to create the new user stories for a new product outside of the existing backlog, which (new user stories) I want to use for the kanban filter , ie. without the new user stories being automatically included in the existing backlog.

[Deleted user]

@Avinash Gautam 

I've just tried it!

Unfortunately, this solution can not work for my project for the following reason:
I can only share the kanban filter for project and / or project group and then for certain roles, eg. all, developers, managers, board etc. but not for single users!
i.e. If I give the permissions to developer or manager for this group of users, then these users can also see and edit other content in my project.

[Avinash Gautam]

Hi @[deleted] 

Please contact your JIRA admin and ask them to create a group with mentioned list of users. Then share you filter with this group. Very possible solution.

Another Solution : Ask them to create a new role for your project like xx-devops-kanban-users. This role can be added in you project roles if you are project admin (you can add individual users to this role). Then you can share your filter for this role. It will work.

These are few options. Also any reason you are not been able to share the filter to individual users? This would have better option.

Thanks!

Avinash Gautam

[Deleted user]

Hi @Avinash Gautam 

Thanks again for your support and practical solutions.

I've contacted the jira admin and found out that I am allowed to create groups and to add users to the groups, not directly in jira but in confluence, which I did not know as a newcomer.

Best Regards

Ashraf