Can a ticket be used across more than one project?

[Muhammad_ Mahiruddin]

One of our team members has most of her tickets in other projects, as she works with multiple teams. Would we be able to have some of her tickets be shared between our project and another project. We would prefer to avoid duplicating tickets if possible.

[Nic Brough -Adaptavist-]

Issues, by definition, belong in a single project.  If you have pieces of work that span different projects, you should look at your project structure (it's not matching how you work), or split the issue into pieces, one for each project that needs to look at it.

It's not quite a case of duplicating it, it's a case of splitting it into the actual tasks that need to be done, and I'd recommend llinking them together, or include them in an Epic if you have Jira Software.

[Ben Kelley]

Another way to do this is to define the JQL for a board to include appropriate tickets from both projects.

As your view of the project is often the board, this might do what you want.

[Hyrum Steffensen _Appfire_]

Hello Muhammad,

I like what Nic and Joe are saying about linking issues between projects. If you would like for both the original issue and linked issue to close out when the other is closed, consider a scripting solution as found in the Atlassian Marketplace. Here is an example on how to do this using Automation for Jira:

Regards,

Hyrum

[Joe Pitt]

If people have access to both projects they can update/read the tickets. You can link the tickets if they are related. However, you can't have them appear in multiple projects.