Adding existing tasks to a new board

[Beverley Griffiths]

I want to create a new client facing kanban board so the client can have access to track selected tickets.

These tickets already exist on another internal board, so to prevent duplication, I want to create a new board, with restricted access permissions and create a link to selected tickets from the Internal board.

Is the possible? Can I get some guidance on how I achieve it?

[Max Foerster - K15t · Accepted solution]

Hey @Beverley Griffiths , and welcome to the community.

Do you want to display the actual issues to the customer? Because you can simply include them on the board. Boards only display issues that are returned by the board filter. But it's necessary to have access to the other issues/projects, or the board will be empty for your clients. The whole permissions will have to be managed in the project and not on the board. There are a few ways to tackle this, but it requires some thinking through your requirements, so like I already mentioned:

• Create a new board, including the issues in the filter, and make sure the client has at least access to view (not edit, etc.) the issues in that specific project
• Create a new board and a new project and mirror/clone the issues. This could be done using automation rules, more advanced workflow configurations, or project/ issue sync apps from the Atlassian Marketplace.

Is that already helpful for you?

Best, Max

[Beverley Griffiths]

Hey Max, thanks so much for your input, I really appreciate it. Yes, I would like to display actual issues to the customer, but only selected ones.

How would I go about mirroring/cloning? Could you provide guidance?

Re clarification on permissions, I'm setting up a new project (Project A). Client will be given access to Project A, but won't have access to any other area. Currently all issues are stored within Project B (no client access - internal only). I'd like to display issues from Project B in Project A whilst ensuring that tickets can be updated within both locations without any duplication.

Is that a bit more clear?

Which would you say is the best approach from your two options listed above?

[Max Foerster - K15t]

Hey @Beverley Griffiths,

please excuse not getting back to you earlier. And thank you for the clarification. I recommend having a look at the Atlassian marketplace:

• Marketplace search "Issue sync" for Jira Cloud 

You will find a few options there, the majority of the will be able to sync issues between two projects, everything or only partial information of the issues, even across instances and platforms. Once configured, this should be the best solution for you (fire and forget hopefully 😄). 

Best, Max

[Beverley Griffiths]

Thanks so much, Max.

I'll take a look! 

Appreciate your time in looking into it,

Bev

[Max Foerster - K15t]

You're welcome! :)

[Umer Sohail _K15t_]

Thank you @Max Foerster - K15t for the awesome tips!  

@Beverley Griffiths 

If you go to the link posted by Max above, you would find Backbone Issue Sync as one of the options. Backbone can help you sync and update selective Jira issues or projects on an instance and keep other projects secured and private. The synchronization can be done in real-time and without any duplications.

In case you need further guidance on how to use Backbone Issue Sync for your use case, please feel free to reach out and book a demo here. 

Regards, 

[Nic Brough -Adaptavist-]

Boards are not containers for issues (projects are), they are a view of a selection of issues.  

If you make a new board for your customers, you can draw in whatever issues you want from any project (and it doesn't matter if those issues appear on other boards)

But you're going to have to revise your permissions - you say project B has no client access.  This means issues within that project won't be shown to your clients even if you include them in the board selection.  You're going to have to give access to project B to your clients.

[Beverley Griffiths]

Thanks so much for this.