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.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot