You can not display an issue in one project as part of another project, because it is not part of the other project.
You could clone the issue and move the new version of it into the second project, but the two issues will be separate entities and handle as such (updates on one would not affect the other)
I think the question here is not really about reporting issues from other projects, it's more about how you should be splitting pieces of work up into issues and putting them in different places for different teams.
So my question is really "what problem are you trying to solve here?"
Hi @Egor Kharlamov ,
Do you mean two would like to track the status of two project issues ? If that the case, create a filter with two project issue and make use of this filter to create a scrum/kanban board based on your requirement.
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events