How to validate user permissions when moving an issue to a different project via automation?

[Ashley Honeycutt]

Every now and then we get a request submitted to a JSM project that needs to be moved to a Jira Software project. 

Sometimes this results in the reporter "losing" the issue because they expect to find it through the portal link that was originally created. To account for this, I created an automation that comments on the issue after it has been moved, tagging the reporter and letting them know the new issue key.

This has helped a lot...except when the reporter does not have access to the destination project.

Is there a way to include a permissions validator in this automation somehow? Maybe if the reporter does not have permission in the project, a notification is sent to the project lead (or some other kind of alert) so they can review if it's appropriate to add the user or not?

Thank you!

[John Funk]

Hi Ashley,

What I do is clone the JSM issue into the Software project and link them - all through automation. Then you can create another automation rule that adds comments to the connected/linked JSM ticket when a comment is added to the Software project issue.