Hi everyone, I have Compass enabled on Jira Cloud and my projects are already switched to “Compass components,” so the built‑in Components field is pulling straight from Compass. What works * component = "Payments Service" returns the work as expected. What does not work * component = "ari:cloud:compass::component/xxx" (the Compass ARI) I want a JQL clause that is stable when the component name changes, ideally by referencing a unique ID. Has anyone found a syntax or workaround that lets JQL match Compass components by an identifier rather than the display name?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can JQL reference Compass components by ID?

Trenton Letz

Hi everyone,

I have Compass enabled on Jira Cloud and my projects are already switched to “Compass components,” so the built‑in Components field is pulling straight from Compass.

What works

component = "Payments Service" returns the work as expected.

What does not work

component = "ari:cloud:compass::component/xxx" (the Compass ARI)

I want a JQL clause that is stable when the component name changes, ideally by referencing a unique ID. Has anyone found a syntax or workaround that lets JQL match Compass components by an identifier rather than the display name?

Accepted answers

Andrei_8eecdk

Hi @Trenton Letz thank you for reaching out.

Referencing components by ID in JQL isn't supported yet, but it is something we've had our eye on for a while, for pretty much the same reasons you mentioned.

It's in our backlog but we don't have a good timeline around when we'll have it available yet.

We'll keep you posted on any progress we make on it.

All comments

Andrei_8eecdk

Hi @Trenton Letz thank you for reaching out.

Referencing components by ID in JQL isn't supported yet, but it is something we've had our eye on for a while, for pretty much the same reasons you mentioned.

It's in our backlog but we don't have a good timeline around when we'll have it available yet.

We'll keep you posted on any progress we make on it.

Trenton Letz

Thanks for the update. Just to confirm, is there a public-facing ticket or suggestion already open for this that I can watch or share with others? If so, I'd love to track it directly.

Keith Furnell

Allowing reference by slug too (for those that use them), would allow for more readable JQL.