Can Issues 'flow' from one project to another?

[Brad Colvin]

As part of transitioning to more offsite and telework we are opening up a number of Jira projects for teams that previously haven't used Jira. One group is essentially a collection of Product Owners. They are looking for a place to coalesce on Epics and Requirements before they are passed to the development teams.

I know that I can move issues from type to type (Task to Story etc.) and from Project to Project. I was wondering what the impacts are if we do this 

• When moving from Project to Project - the project key changes to the new project correct? Is there any history information saved? What project if came from? 
• I believe that the ranking of these items would also change/fluctuate when moving them to the new project(s) the Development team actually uses a multi-project kanban board and things moved to this board should get new priorities. 

What else am I missing?

[Nic Brough -Adaptavist-]

Jira will keep the existing history when you move and also record all changes made to the issue when you move it.

Ranking is a global thing, so the rank of an issue will not change when you move it to a new project.

[Joe Pitt]

If you move an issue it gets a new key, however the old key is maintained and can be searched for. 

I don't know about the ranking