Hi Rodolfo,

You sure can. Just click the "Save it as a filter" link after you have run your JQL query.

Is it possible to create filters using the Jira Query Language?

As part of 4.0 with the introduction of the JIRA Query Language you will be able to construct a query to achieve this.

We have introduced a parent function that when passed an issue key will return a result of all sub-tasks.

For example: parent = jra-nnnn

There is a column, 'Sub-task' listing all sub-tasks in Issue Navigator.

Can we have another column, 'Parent', listing the single parent. I'd like to extract a list of sub-tasks, ordered by Parent id.

Hello,

It is really annoying when I need to change sub-tasks of a given task especially that sub-tasks don't inherit much from the parent. I have to go one by one as there is no way to get these sub-tasks in the Issue Navigator.

Is this so difficult to add a search by parent key?

Cheers,
Michal

A more open-ended search would be great, as bulk change operations seem to be restricted to search results.
Would it be possible to consider reqular expression and/or SQL style search terms in addition to (or instead of) the current set?

One could search for subtasks by (something like):
SELECT sub-task FROM myproject WHERE PARENT==the-parent-tasks-[xx-yy];

This would be of great help. I work as a consultant, and have helped several teams start using JIRA. This is always requested as a feature in the first few days. Does anybody know about a plugin or macro which does this?

Would be great to see this one too. We have some customers that want to 'filter' by Issue Key, and get all the sub-tasks under that issue key.

Hi Stafford,

Due to the number of other more popular feature requests there are currently no plans for implementing this feature.

Cheers,
Anton

The lack of support for this feature has strongly affected our usage of JIRA due to a business requirement that sub-tasks be bulk-editable. We've had to follow the path of using regular issue types instead of sub-tasks but it's not the ideal solution.

Is this on the roadmap to be implemented in an upcoming version?