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

Company managed project issues in template project issue list


We plan to use company managed projects. For that we have created one general company manged project (lets call id X) to be used as template for other projects. We had one project created before as team managed project. For this project we created new company managed project (lets call it Y) using template and bulk moved all issues under new project. 

For some reasons we can't see project Y issues from project X all issues list when in filters project Y is selected. Same problem is when new issue is created in Y. But when we created another new project using as template then there is no problem.

So this is the view that shows all issues and issue N10249686-8 is shown as wanted. 

Now when adding project filters and including issue N10249686-8 project we don't see issue N10249686-8

We just can't find the reason why project BHC issues are not shown.

1 answer

0 votes
John Funk Community Leader Jul 13, 2022

Hi Martin,

Just for clarity, can you change the filter in the second image to use the project keys instead of the project name? For instance, it would look like: 

Project in (ABC, DEF, 123)

Hi John,

When i use keys everything works. But JQL shown was auto generated when selecting project from dropdown.

Interesting is that new projects issues are shown correctly but when issues have been moved over then don't

John Funk Community Leader Jul 14, 2022

I think the project names have gotten intertwined somehow. I would just use the project keys and you should be fine. 

Using the key is an option but not that comfortable. Also it shows that there is some kind of problem when bulk moving issues from one project to another.

It isn't actual solution for a problem.

John Funk Community Leader Jul 19, 2022

Just because it happened one time doesn't mean it is a problem every time when moving from one project to another. I have done that dozens of times with no problem. 

And using the project key is just as comfortable as using the project name - again in my opinion. I am not sure what was not solved for you in this instance - what can you not do that you are trying to do? 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events