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; } } }

JQL to check if an issue is QA Ready vs creating a new workflow status.

William _Bill_ Klein

Using Jira Cloud & Github Cloud.

My company prefers to keep the number of workflow statuses to a minimum. Looking for JQL to use as a quick filter on a scrum board to see if an issue is Ready For QA. Have been trying different combinations of the development and buildState fields. Closest I have come to is:
(buildState !~ failed and buildState !~ "in progress" and buildState !~ failed and buildState !~ unknown) and development[pullrequests].open = 0 and status not in (done, cancelled) and project = abc

The above still shows issues if there is a declined pull request.
Any thoughts on how to improve this JQL or is there a totally different approach to take?

Accepted answers

William _Bill_ Klein

My need changed a little, need to force the first 3 characters to be PRJ:

This solved my problem:

issue.customfield_10038.matchAll('^(PRJ){1}+\d+$').length > 0

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

JQL boils down to a simple binary question when you expand on it - "does an issue meet these criteria?".

We don't know how you are working, and hence can not really tell you a lot about the JQL that might find the right issues. But if you can work it back to the binary "what specifically makes an issue "QA ready", you should be able to build JQL to find that.

Break this down to the most basic part of it - you've said status is not the thing that determines if something is "QA Ready", so you need to look at what else makes it that.

The opinionated bit: I would strongly recommend telling your company to stop being over-minimalist and recognise a status as "QA ready" as it's clearly part of your process. I am thinking of a very common (but not Agile) and simple case where developers write some stuff and then throw it over to a test team - when a developer finishes a story, they move it into their last column to say "done as far as this team is concerned" (a status of "dev done" or "QA ready"), then the test team sees that as their "to do" column.

William _Bill_ Klein

Agree with the opinion and will continue to work on getting a status.

As for the search I am trying to build:
- Latest\last build is successful.

and

- No outstanding\declined merge requests.

Did some testing with the buildState field. Searching for successful value does not check the latest build but any build which has passed in the past.

William _Bill_ Klein

My need changed a little, need to force the first 3 characters to be PRJ:

This solved my problem:

issue.customfield_10038.matchAll('^(PRJ){1}+\d+$').length > 0

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

jql