Issue when using text field with issueFunction in Jql

rajeswari saravanan

I have one jql which im filtering with not in last comment and Iam filtering it with email address.Its fetching wrongly

jql:

project=xxx snd issueFunction not in lastComment(“by 12345”) and “Email Address”~”yyy@zzz.com”

Here in the above jql there is one issue with email address mentioned but the last comment is by 12345,but here I mentioned not in last comment but its populating the issue with email address with last comment by 12345 user.

Its an issue not while using dropdown values,only happening when using text like email.Any clarification why this is happening.

Sandeep_e4emhu

Based on the JQL query you provided, it seems that you want to filter issues where the last comment is not made by a specific user ("12345") and the email address contains "yyy@zzz.com". However, you're experiencing unexpected results where the query includes issues with the specified email address and the last comment made by the user "12345".

The issue you're encountering might be due to the way Jira handles the search logic. When using the not in operator with the lastComment function, it retrieves issues where the last comment does not match the specified criteria. However, other comments that meet the criteria may still exist, and they can affect the results of your query.

To work around this issue, you can try using the != operator to exclude issues with comments made by the specific user. Here's an updated version of your JQL query:

project = xxx and issueFunction not in lastComment("by 12345") and comment != "by 12345" and "Email Address" ~ "yyy@zzz.com"

By including comment != "by 12345", you ensure that issues with comments made by the user "12345" are excluded from the results, regardless of whether they are the last comment or not. This should provide the desired filtering behavior while still considering the email address criterion.

Remember to adjust the query based on your specific Jira configuration and ensure that the field names and values are accurate.