Advanced Search with JQL Won't Filter Suggested Users based on Search Text

Question

I'm specifically working on trying to change my Slack notifications using JQL. When attempting to use the `assignee` field and looking for my name I can't get this to work with my username, I'm assuming because of recent GDPR changes. However, as has been suggested I trying to just type my name and I only ever get the first 15 users where their names start with "A" and I'm looking for my name which starts with "T". The search/filter simply does nothing to filter the autocomplete results.

Daniel Eads · Answer

@tnolte sorry you've been having some trouble getting the notifications set up!

The good news is that we're close to shipping API-80 - Personal Jira Notifications in Slack . It's in early-access right now and you should be able to get the type of notifications you're looking for with minimal configuration. As we're in the process of incrementally rolling out the feature to Jira sites, it's possible that it's not quite available to you yet. Once it is, you should get a message from the Jira Cloud app in Slack:

You can also try messaging notify to the app right now and see if it gives you the configuration options. If not, check again in the coming days!

tnolte · Answer

Well, just to follow up, JQL is still not working. I tried this:

```

assignee = ############# AND lastCommentBy != #############

```

Using the GDPR user ID and the result is that I get no notifications for anything. I'm trying to get notifications for just when other do things to tickets assigned to me and not get notifications for everything I change on the ticket. I don't need to be notified about the things I did myself. So frustrating.

Daniel Eads · Answer

Hey @tnolte , welcome to the Community!

Thanks for describing the behavior you're seeing with adding user fields in the JQL filtering for Slack notifications. I was able to reproduce the same thing on a test instance and have filed a bug with our integrations team. You can track this on our public Jira instance at API-231 .

With a little extra trouble, you can get the filter working currently. By running the filter search you want to set up in a regular Jira issue search outside of the Slack subscription configuration, you can get the username picker to filter correctly and have it complete the GDPR-compliant user ID. Once the filter is working in a regular issue search, you can copy and paste the JQL into the Slack subscription configuration.

Cheers,
Daniel | Atlassian Support