How to setup a Kanban board accessible for customer?

Henk van de Goor February 19, 2018

Hi,

I have a simple question but can't find a simple answer.

We use the cloud version of Atlassian and would like to setup a Kanban board that we want to share with our customer. They want to be able to create Kanban items, move them etc.

In what order do we have to do what and what are the (pre?)requisites for this?

There should be a simple "wizard" for stuff like this or maybe even a 'template' but we totally get stuck after creating the project.

Instead you get stuck with a tool that has a million options, making it impossible to do simple tasks like this...

Any input or pointers to the right resources would be very appreciated..

Wish the it was as simple as Trello!

Henk

 

 

 

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 21, 2018

In order for a user to see or interact with a Jira Software board (such as kanban or scrum), that user needs to have Jira Software application access first.   Without this the user cannot access any of these board features specific to Jira Software.

 

Steps on how to do this are in https://confluence.atlassian.com/cloud/manage-application-access-744721629.html

 

Could you clarify the term 'customer'?  Is this a user in Jira Service Desk's customer role?  If so, then in Cloud, you won't be able to grant that user access to Jira Software per Access of Jira Service Desk customers.

 

If that user has application access, then the next step is to make sure that they have permissions to see both the issues on that board and have been shared the filter on that board.   I'd recommend checking out Managing shared filters and Managing project permissions.  You will need to first look at the filter for this board to understand which project(s) this board is pulling issues from.  From there, you can then go to each of the projects in question to make sure that this user has been granted the needed permissions to see the issues that will appear in those projects.

Suggest an answer

Log in or Sign up to answer