For this case I think the best is to clone the issue in different projects and have them all pointing (linked) to the same parent issue.
An issue can be associated to only one project, but you can link to it from any other issue in any other project.
Alternatively, you could also use labels (or a custom field) to differentiate between "projects" affected and have all issues created under the same umbrella project (something like cross project issues).
This was raised as a feature request some time ago: https://jira.atlassian.com/browse/JRA-23785. The issue was resolved as Won't fix. You may want to add your own comments there.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs