How to exclude work items where summary is equal to TEST in JQL

[Joshua Redel]

I have to use JQL for a search that connects to a slack integration, and I explicitly want to exclude where the name of the work item is "TEST". However, summary only seems to search for !~, which means anything with TEST in the name would get excluded. How can I exclude an item whose name is TEST specifically? 

[Marc -Devoteam-]

Hi @Joshua Redel 

Based on your requirement and the response from @Trudy Claspill would it not be simpler to create a new work type called "Test"?

Use this work type for testing, then in a JQL its way simpler to exclude a specific work type, then basgin this on a test field like summary.

[Trudy Claspill]

Hello @Joshua Redel 

Welcome to the Atlassian community.

Do I understand correctly that the items you want to exclude have only the text TEST in their Summary, and no other text?

What I have found is that the !~ can exclude items based on a phrase, but if it has only a single word then it excludes all items that contain that word anywhere within the field.

Is it possible for you to change the name of the items to a unique multi-word phrase like "TEST ISSUE"? 

[Joshua Redel]

Yeah, so I can, but it's really hard to enforce that across a team of 50 engineers — just telling them "call it TEST" is easy, but telling them "call it TEST ISSUE" is much harder. Is there really no way to just say you want when summary doesn't equal something? Is it perhaps possible using an embedded AQL query or something?

[Trudy Claspill]

AQL is for querying Asset related data. Do these have some relationship to Asset objects?

In an Automation rule you can use string functions to determine if a text field contains just "TEST".

You could use Automation Rules to change or existing items and new items as the get created.

Or you could add a custom field that is more easily filtered upon, and ask the engineers to set that or again use Automation Rules to set it. 

[Joshua Redel]

The problem is that "on create" is also when the Slack Integration runs, so there'd be a race condition for any automation to update a field before the slack integration catches the item and spams our slack channel.

[Joshua Redel]

(oh, and sorry, no assets under consideration, so no AQL — makes sense, thanks)