-
Suggestion
-
Resolution: Unresolved
-
None
-
137
-
7
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
It should be possible to nest JQL function calls. At the moment there are no builtin JQL functions with which it would make sense to nest them but it would be helpful for custom JQL functions.
- relates to
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-21936] Allow nested JQL function calls
Please, please support referencing saved filters directly within another JQL query. The limits on this functionality is blocking my team from effective reporting and sprint planning.
use case:
issuetype = Epic AND "Parent Link" in (filter("FilterID"))
I cannot convince my organization to spend 10K per year on licensing so that I can filter boards effectively.
8b12fff371d0 I can't really show. But let's say I create a filter like All issue of type story for a given release and then I save that as a search filter making sure the that issue key is one of the fields returned in the filter and call it Current Release Issues. Now I go in and create a new search filter called QA tasks for Current Release. In that filter I select all sub-tasks for QA where the Parent is in Current Release Issues.
So something like: project="My Project" AND issuetype="SubTask" AND summary ~ "QA" AND Parent INFILTER ("Current Release Issues")
I came here in search for the way to fild child issues of issues from another search result.
It seems like is not possible yet
fce57545551c, can you show an example of what you say in your comment?
Upvote, alternatively you could reference a filter and sub-query off of that.
We have a filter that collects a specific set of relevant epics.
We also have a set of filters using that result set of epics in the parent field of other issues. Currently, we have to update every single filter and do so every single time the set of epics changes. This is really cumbersome and error-prone.
The ability to do something like this would make a huge difference:
parent in (subquery(filter=1000))
I guess not much hope for Atlassian to do anything, 555 votes, 13 years in the waiting,....
This was logged almost 15 years ago and has over 600 upvotes. Don't let Atlassian fool you - they want you to buy plugins because they get a % from the money paid to those developers. Why on earth would they provide native functionality or improvements to their product if they can make money off of developers who do the work on their behalf for free?