Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


How to exclude specific fields from updated event so I can find only specific events


I want to track tickets that the Engineering team didn't provide answers to/action on, so I was using the filter below, however, if I add any comments or update fields it counts as an updated event so that those tickets won't pop up on the filter. 


How I can be more specific with my query, for example, is there is a way to exclude actions from specific group ( Support team ), so only actions from RD team will be counted as updated? 


issuetype in ("Customer Bug", "Customer issue") AND status not in (Done, Release, "QA APPROVED", Archive, QA, "Pending customer") AND updated < -14D ORDER BY updated ASC



1 answer

0 votes
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 16, 2022


Unfortunately, an update event (out of the box) applies to any update to the issues and cannot be further defined or customized based on my knowledge.

However, here is an idea for you to achieve what you wanted -

1) Create a customer field (i.e. a number field) treat it as a counter field which will increment when your support team members update the issues only.

2) Create an automation for Jira rule trigger by Issue Updated + a conditional check  (if/else) using "User Condition" to check if the user who triggered the event is a member of your support team.  If so, then execute the Edit issue action to update the custom field defined in step #1.

3) Modify your JQL to include a check for the value of the custom field.  The custom field should only be not Null (not = 0) if the issue update action was done by your support team members.

The only drawback of the idea is it may be creating an endless loop.  However, I have not try it yet, thus I cannot be certain.  But, it is an idea for you to think about.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events