Sharing Jira issues between projects

unknown

Hi,

Working in Jira V7.0.10. 

I want to see Jira issues created in other projects displaying in my project for one specific board.

Situation: Various teams with their own projects want members of my team to work on Jira issues and we want to have one single view of everything we are working on via one board. this needs to be in our project. There may be other team members working on the same Jira issue outside of my team. My team do not want members of other teams logging time to our Jira issue. 

I thought of cloning but I can't do this between projects. Can I?

I thought of us creating tasks in our board view from a main story in another project. Can I do this?

Rudy Holtkamp

Hi @[deleted],

You can show issues from other projects on your board by including them in the board filter. 

project IN ("project team 1", "project team 2", "project team N") ORDER BY rank ASC

Note that you and the people viewing the board need to be able to have browse project permission in the mentioned projects otherwise they will not see issues from other projects. You also need to have schedule issue permission in all projects in order to rank the issues on your board.

Note2: For Kanban this is not a problem, for Scrum it can be, because you have sprints in your project and in the projects of the other teams there are also sprints, which end up on your backlog. This can be confusing for users.

"My team do not want members of other teams logging time to our Jira issue. " this is also enabled by a permission "Work On Issues", just make sure only project members have this permission. It is best practice to have your permission scheme setup with roles. If you do so, you can have a role Developer (your team) that has that permission and a role 'Users' that doesn't.

"cloning but I can't do this between projects", you can clone between projects, but you need an app for it. You can clone in your own project and then move the issue to another project. I would not recommend this way of working, since you duplicate information, which you need to keep in sync.