Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

External ticket collaboration

My firm provides SOC 2 examinations for SaaS companies and the service requires a good amount of questions and requests. Today we use Notion for that collaboration but it’s adding an additional tool outside my clients workflow and would seemingly be easier for them if we were able to add Jira tickets directly to one of their boards (something like 70% of my clients use Jira). 

What would be the best way to set this up? Is it just giving us a guest role to a specific board? 

If we created a standard template for this (as many of our requests are duplicative) and invited them in as guests would it be easily accessible with all there other boards? My knowledge of Jira is not extensive 😅 thank you in advance 

1 answer

0 votes

Welcome to the community, @Mike DeKock,

I am Marlene from codefortyine

My suggestion would be to create a template project with template requests/issues. Then clone the project including its issues for every new client using our app Deep Clone for Jira.

You could either clone the entire project including its issues, or bulk clone and move the requests (if you want to create the project manually).

The advantage of having separate projects per client is that you can give permission per project to clients. It's also possible to work on the requests without interfering with the workflow with other clients, and have a project board for every client.

You can read more about a similar use case in this article. Please note the article is from 2019, so Deep Clone has a lot more functionalities today:

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events