Comments on Jira Service Management Board Tickets

David Waldie May 20, 2021

Currently I am finding that if there is a ticketed that is linked between a Jira Software Project Boards (as a Software Project) to a ticket on a Jira Service Management Boards (as a Service Project), when the ticket on the Jira Software Project Boards is either set to Done, Closed or Closed - Not Required, it adds a comment to the Jira Service Management Board ticket with my name and the requestor of the Jira Service Management Board ticket receives an automatic email stating the new status was modified by myself.

The strange thing with this is is that I am not making the modification of the Status on the Jira Software Project Board ticket but the change is being made by other users of the Jira Software Project Board.

I have gone through all the settings that are available to me on the Jira Software Project Boards, Jira Service Management Boards and within the Jira Software and Jira Service Management but have not found any reference to my profile or email address that would cause this to happen.  I have found that it looks like that this could be happening when I am setup as a Watcher of the ticket on the Jira Service Management Boards but I am unsure that this could be the cause as there are other users referenced as Watchers.

Any information as to why this could be happening and how to resolve would be greatly appreciated as this is now starting to impact users and the quality of communication that is being provided.

1 answer

1 vote
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 20, 2021

This is most likely due to the fact that there is an automation rule that is running in your name. Go to the project settings/automation and look at both new and legacy Automations for a possible rule that explains this

David Waldie May 20, 2021

Hi Jack,

Thanks for your reply.

I have had a look at the Automation under the Jira Service Management Board and found some Legacy Automations that had the "Run rule as" option set to the Project Default which is myself.  I have changed this to be "User who triggered the rule" and hopefully this issue will not re-occur.  I will monitor for the time being.

Thanks for all of your help.

David

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer