As a JIRA admin - can I remove myself from an issue's list of participants?

[Dave Donnelly _Sensata_]

As our company's JIRA admin I sometimes step in and comment on issues to give users help or advice on using JIRA. Sometimes they need me to transition issues back through the workflow if they clicked on something by mistake. I also encourage them to assign issue to me if they have a query. I assign them back to users along with an answer.

An unfortunate side effect of this is that I then get put on the participants list and start to receive updates about the issue, the resolution of which, I am not actually concerned about. I can't see any easy way to remove myself from the participants list from a UI perspective. Any ideas...?

(PS: Putting the "Issue Participants" field on the edit screen doesn't seem to work...)

Many thanks,

Dave

[Nic Brough -Adaptavist- · Accepted solution]

No, participants is a "dynamic" field - it works by reading other fields and adding them all together. There's no way to remove someone because the references to them only exist in other fields. You'd need to remove them from those fields to enable the removal.

I've seen it rewritten in a couple of places (and I've done it myself once), it's actually quite easy to add in code that can do more clever stuff. In my case, I wanted to add the contents of another user picker, but for you, you'd want a line that says "unless it's Dave" when it's iterating through the fields. (Or "remove Dave" before committing the data. Or maybe "don't add if they're actually an admin who only commented"). If you installed a modified version and then re-indexed, you'd be sorted.

[Dave Donnelly _Sensata_]

Thanks Nic.

[Dave Donnelly _Sensata_]

Raised https://jira.atlassian.com/browse/JRA-25960 to have this permission / ability added as a feature. Please come and vote if you think it would be useful for you.

[Nic Brough -Adaptavist-]

Um, I still don't think it makes any sense. Participants is a derived field. To remove yourself from it, remove yourself from the rule that catches you.

Or, come up with a different rule, and code that.

[Joe Pitt]

You do realize the participant field is implemented in the JIRA Toolkit plug-in which is marked as unsupported, not in the base JIRA code. Have you polled your users to verify they like to get emailed for everything they are participants in? Almost all users I've encountered prefer fewer emails unless they chose to watch an issue.

[Dave Donnelly _Sensata_]

<necropost_I_just_noticed>

Nah - they do what they are told... ;)

</necropost_I_just_noticed>