Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JQL deploymentName working partially

Steeve Le Dréau May 28, 2025

Hello,

 

I'm currently trying to set an automation using deploymentName criteria.

It works partially and I don't understand why.

Here is the detail of an issue deployed on multiple environments : 

 

Capture d'écran 2025-05-28 112439.png

 

As you can see, three different deployment numbers are bound to this issue.

In the issue navigator, using this deployment number as a filter works

Capture d'écran 2025-05-28 112601.png

But when I try on the 2 other deployment names, there is no result appearing.

Capture d'écran 2025-05-28 112802.png

Can anyone explain my why one deployment name is working and not the others please ? 

Thank you

1 answer

1 vote
Chitra Nagdeo
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 29, 2025

Hey @Steeve Le Dréau ,

 

Welcome to Atlassian Community!

Could you try below syntax and confirm if the issues are fetched by JQL

deploymentName ~ "19856"

I took reference from article: JQL developer status

Regards

Chitra Nagdeo

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events