When a Scrum or Kanban board is launched, it execute the primary Filter and gets a results set of JIRA's that match the criteria.
Our question is: do the other places on a Board which can use JQL, for example, Swimlanes and Quick Filters, do they only look at the results set from the primary Filter; or do they search the entire JIRA instance?
The reason for the ask is to confirm whether we need to re-specify key attributes in these other JQL statements. For example, if the primary filter pulls in JIRA from a specific JIRA Project, do we need to have the "Project =" phrase again in these other board JQL statements, or is the "Project =" not needed again since these other JQLs are only looking at the original results set?
Hi @CAV from TXN and welcome to the community! JQL statements would be sub-queries of the filter. So no... You do not need to retype "Project = " (at least in situations where you're working with a single-project board).
Thanks for the quick reply.
First, let me clarify that I am working with single-project board.
Here is a follow up question.
Are there any advantages or disadvantages to re-specifying attributes on the sub-queries? In other words, would including the "Project =" in the JQL sub-queries cause it to run faster or to run slower?
I'm asking because we have been advised to include "Project =" again in order to help the overall performance of our JIRA instance. I'm wondering that is sound advise or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To my knowledge there are no advantages. You're executing a query against a result set that is already filtered.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.