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?
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
Aha, thanks for clarifying @Alex Koxaras _Relational_ , now that you mention it, never thought of it, clever!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thou if you try type in standardIssueTypes() => Will also return Epics as well
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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. :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
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.