When we move a ticket from project A to Project B of Jira within the same Site, the informant loses permissions and does not receive the comments made by the person responsible for the ticket in project B, and I don't know why this happens.
When you move a ticket between projects it is important to remember that this then changes the schemes associated with the ticket. In particular the permission and notification schemes in your scenario.
If you look at the permission and notification schemes for the two projects you will be able to see where they differ. This could be as simple as the user not being a member of the Project B and so not getting any of the access/notifications. Or it can be more complex if the projects use roles. Although the adding a user to a role is often simpler than other project membership.
What you are seeing is expected behaviour as when a ticket is moved between projects it loses the connection to the initial project (and its associated schemes) and is now part of Project B (and its associated schemes).
Hope this helps with understanding the behaviour and how you can change the schemes to allow access/notifications.
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events