What is the Field in JQL to get the user who just updated, created or closed the Task.

Question

What is the Field in JQL to get the user who just updated, created or closed the Task. see I have my Slack configured with my Jira so that if anyone creates, closes or updates a task on which i am assignee it will send me notification but the problem is that when i myself closes updates or creates an issue i get notifications. my JQL for now is this:

assignee = mahadasifdev

but i want something like this:

assignee = mahadasifdev AND updatedBy != mahadasifdev

so that if i update the task or something like that i dont get bombarded by the notifications because i already know i am updating the task.

Any kind of help will be Appreciated.

Thank You!

Hannes Obweger - JXL for Jira · Answer

Hi @mahadasifdev

welcome to the community!

Just to add to John's great answer: If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets.  It also comes with a long list of so-called smart columns that aren't natively available, including last updated by user.

This is how it looks in action:

As you can see above, you can easily sort and filter by the last updater, and also use it across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

Once you've narrowed down your list of issues, you can work on your issues directly in JXL, trigger various operations in Jira, or export your issues with just one click.

All this just works - there's no scripting or automation whatsoever required.

Any questions just let me know,

Best,

Hannes

John Funk · Answer

Hi @mahadasifdev - Welcome to the Atlassian Community!

If you create an automation rule for the update, you can use {{issue.initiator}}