I need to update 19 forked repos,
each update requires

• 1 click to open the repo
• 1 click to select settings
• 1 click to get to details
• 1 click to get advanced
• search the branch (forks include all branch of the sources I need to wade through all the unneeded branches from the source) but that's another unsolved issue
• scrolling down to get the save button
• clicking the save button
• closing the window

thank you for letting me waste my time by not providing an automated solution

There is unfortunately no option for us to do that.

This is working for me. Go to Project settings --> Automation ---> New rule ---> type in Issue Moved

Then select your source project and target project. click save. Select  Then: Add an action and search for Send slack message. You need to create a slack webhook url and customize your slack message in the description. Select your channel to send the message and save it. Publish the automation.

Is there any updates on this?

Definitely would like this  

Has any progress been made at all on this?

We have the same issue as described by Bobby Crowell. I ticket is created in wrong project and moved to the correct one, there is no slack notification and the ticket goes unnoticed.

Here's what we're doing in the meantime with a ScriptRunner event wrapper. We listen for Move events, and then fire off a Create event.

This would be very helpful to have. 

We have several teams who don't actively engage with Jira and only respond to new tickets as they pop up in slack. When a request gets created in the wrong project and then moved into their project, they are not notified as they would be for a request newly created in their project.

This encourages duplicate ticket creation, missing requests, and/or deleting Jira tickets in favor of newer ones.

We'd definitely be interested in seeing this fixed.

Has anyone tried simulating it with JQL in any way?

Any updates on this? This is something that's definitely lacking to be able to provide visibility to Jira Issue changes.

Just enabled my subscription today.

Any update on this issue? This would actually improve Jira drastically. Currently, less in touch clients attached to projects do not see when issues are updated. This type of posting of issued moved would increase their connectivity without having to manually push them to an issue.

Please prioritize this if possible.

We're still hoping and waiting for this. When will this be considered as interesting to implement?

Is there any update on this? This would be very helpful.