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

"Issue does not exist or you do not have permission to see it." Error on Deep Clone Add on App

I am trying to use the Deep Clone add-on to clone template projects.  I created a custom permission scheme for template projects and I have assigned myself a role on the project and granted access to all permissions in the permission scheme to that role.  When I try to clone I get an error "Issue does not exist or you do not have permission to see it.".  I can see both the issue I am cloning and the issue that is created before it fails (it appears to be failing after creating the cloned issue successfully but failing while trying to clone the issue creator and assignee.



In the absence of getting this to work does anyone have any alternative options to cloning template projects?  I appreciate any feedback as we are ready to start templatizing our projects.  I appreciate any reply at all.  Thank you!

1 answer

1 accepted

0 votes
Answer accepted

Hi @Zane,

I am Marlene from codefortynine.

Thank you for contacting our support. We have already answered to your request. 

The warning messages probably relate to the app not having the appropriate permissions. 

We hope your problem is resolved soon.

Yes!  This issue is resolved :)

To help the next guy,  the resolution was to make sure the Project Role "atlassian-addons-project-access" has access to everything.  I always removed it because of OCD and it never effected anything before.  Now I know some plugins need it to work right.  The more you know!



Thank you for sharing that with the community, @Zane . I am really happy to read that your problem is solved :) 

We've added a new page to our documentation that describes the required permissions for Deep Clone for Jira. You can learn more about it here.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events