JQL query return the same result

Edward Quinito
Contributor
November 6, 2022

What is the difference between these JQL :

1. type in standardIssueTypes()

2. type not in subTaskIssueTypes()

I found that both return the same result, or is there any specific use case for both?

e.g. No. 1 usually used for board filter, No. 2 usually used for reports.

or both 2 have the same usage?

2 answers

2 votes
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 7, 2022

Hi @Edward Quinito and welcome to the community!

1. type in standardIssueTypes() => Will return only standard issue types

2. type not in subTaskIssueTypes() => Will return standard issue types and Epics as well

Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 7, 2022

Aha, thanks for clarifying @Alex Koxaras _Relational_ , now that you mention it, never thought of it, clever!

Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 7, 2022

I had to edit my answer twice, since your reply got me thinking and to be honest I was confused. Thankfully, my answer will stay as is. THe 2nd statement will return Epics as well.

Edward Quinito
Contributor
November 7, 2022

hi @Alex Koxaras _Relational_ 

Thou if you try type in standardIssueTypes() => Will also return Epics as well

Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 7, 2022

@Edward Quinito hmm... you are definitely not wrong. According to the documentation:

Perform searches based on "standard" Issue Types, that is, search for issues that are not sub-tasks. See also subtaskIssueTypes().

Tbh I would expect to bring only standard issue types, excluding Epics. However, it seems that it yields any issue type that is NOT a subtask. So basically what you say is correct. They seem to be the same.

Like Edward Quinito likes this
Edward Quinito
Contributor
November 7, 2022

@Alex Koxaras _Relational_ 

I also expect the JQL not to return Epics, but since it also return epic, then I need to add AND issuetype not in (epic) to show on what you mentioned on above. 

Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 7, 2022

@Edward Quinito 

Yes, you are correct. I've looked also to see if there is an open bug for this, but wasn't any. So I would expect, based on the doc as well, that this behavior is normal. :/

0 votes
Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 7, 2022

Hi @Edward Quinito welcome to the Atlassian Community!

Good question. Actually, the result is the same. I couldn't find a use case (yet) where the result is different. Watching this question as I'm interested in other answers.

Edward Quinito
Contributor
November 7, 2022

Yes they do both return the same result, and I don't find the use case yet also.

This is the reason why I asked this question. Is there any practical use as for board with multiple project type, for reporting, etc?

Suggest an answer

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

Atlassian Community Events