I have a search I execute every day to show me the Issues I participated in during the past 24 hours. I use the "Participants = currentUser()" as part of the query.
Today I noticed that one of the Issues I know I worked on did not appear on the list. In that Issue I edited a long text field and I transitioned the Issue to a new status.
But I am not shown as a "participant" in the issue.
The issue is "HF-2840" in my database. This query gives zero results:
key = HF-2840 AND Participants = currentUser()
And neither does this:
key = HF-2840 AND Participants = georgec
Pariticpants only tracks assignees, reporters and people who have commented on the issue. It doesn't track other edits, transitions etc.
You can easily capture workflow changes by improving the query.
Participants = currentUser() and status changed by currentUser()
But issue edits will be a problem. You will have to add a comment while editing if you need it on the participants field!
The participants field is coded to say "reporter, assignee and anyone who has commented on the issue". It doesn't scan for "used a transition" or "Edit".
I've used the participants field code as a base for other similar fields a few times now (e.g. reporter, commenters and person who changed priority), but I'm afraid the off-the-shelf one doesn't have any configuration to allow the question to be changed.
But the comment requirement is a real pain and badly detracts from the ease of use. I only require a comment when I really need one, for example, when something is failed or reopened.
However, Jobin's extension of my query will cover 99.9% of the Issues I was missing before.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot