Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-59181

Ability search for all issues under a given Epic (including subtasks)

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update – 14 February 2017

      Hi everyone,

      We have recently added support for this in JIRA Cloud with the release of a new JQL function called parentEpic. Searching with parentEpic will return all the issues in the specified epic(s) AND their sub-tasks. The syntax is a little bit different than a standard JQL functions – it's more like searching with a field. So

      project = JRA and parentEpic = JRA-123

      will return all issues and sub-tasks in the JRA project that are in the JRA-123 epic. The function also supports the != , IN , and NOT IN operators. So you could also search something like

      project = JRA and parentEpic in (JRA-123, JRA-456)

      and you will get all issues and sub-tasks in either the JRA-123 or JRA-456 epics.

      Refer to the documentation for more information. Happy searching!

      Note: Currently we don't have a timeline on when this will be released in JIRA Server; however we will provide an update once we do.

      Dave Meyer
      Senior Product Manager, JIRA

      Problem Definition

      As a manager I want to be able to filter all the issues related to a specific Epic. Right now it is not possible to filter the subtasks without using a third party for this purpose. I believe this is a common need and should be added to JIRA Standard JQL search.

      Suggested Solution

      Create a function to return all issues related to Epic, like the one provided by tempo parent in tempoEpicIssues(XXX-####, YYY-###, ZZZ-####).
      This would allow searchs like: "Epic Link" in (XXX-####, YYY-###, ZZZ-####) OR parent in tempoEpicIssues(XXX-####, YYY-###, ZZZ-####).

      Workaround

      Install and add-on to provide the list of issues in a given Epic so the above suggestion can be used.
      This thread talks about some options: JQL to show all issues AND subtasks in the Epic.

            [JRACLOUD-59181] Ability search for all issues under a given Epic (including subtasks)

            Stuart.Sinclair added a comment - - edited

            +1 to Haddon Fisher's comment.

            I want to build a dashboard for a product that is shared by my team and another. The product will have an ongoing stream of epics for a period of quarters, but it doesn't make sense in general to make it its own project outside the context our existing projects. When were were on a local Jira server we had a plugin that allowed me to subquery for Epics based on a combination of keywords in the summary/name, status, and project, and pull in all their children. (I would be fairly happy with keywords in the name or summary if I had to pick one.)

            Essentially it's a pain to have to go to another screen and modify the filter for this dashboard every time we create a new epic related to this product. I will do it, but the rest of my team won't, which makes the dashboard become untruthful quickly. They are willing to follow naming conventions. 

            It's also frustrating, because as I create epics when working with my stakeholders, they aren't immediately available within the dashboard or board.

            All of which is to say, I think this is an important feature. 

             

            Stuart.Sinclair added a comment - - edited +1 to Haddon Fisher's comment. I want to build a dashboard for a product that is shared by my team and another. The product will have an ongoing stream of epics for a period of quarters, but it doesn't make sense in general to make it its own project outside the context our existing projects. When were were on a local Jira server we had a plugin that allowed me to subquery for Epics based on a combination of keywords in the summary/name, status, and project, and pull in all their children. (I would be fairly happy with keywords in the name or summary if I had to pick one.) Essentially it's a pain to have to go to another screen and modify the filter for this dashboard every time we create a new epic related to this product. I will do it, but the rest of my team won't, which makes the dashboard become untruthful quickly. They are willing to follow naming conventions.  It's also frustrating, because as I create epics when working with my stakeholders, they aren't immediately available within the dashboard or board. All of which is to say, I think this is an important feature.   

            Haddon Fisher added a comment - - edited

            Forcing us to explicitly define the keys whose children we want negates most of the usefulness here. This function needs to accept a sub-query instead so that we can look for the children whose epics meet the criteria we have, and not need to manually maintain a list of keys.

            UPDATE: For anyone looking for what I have described, please howl at the void towards JRACLOUD-21936.

            Haddon Fisher added a comment - - edited Forcing us to explicitly define the keys whose children we want negates most of the usefulness here. This function needs to accept a sub-query instead so that we can look for the children whose epics meet the criteria we have, and not need to manually maintain a list of keys. UPDATE: For anyone looking for what I have described, please howl at the void towards JRACLOUD-21936 .

            Daniel Turczanski added a comment -

            Hi! Many more epic related JQL keywords are supported after installing our plugin. Make sure to check out the JQL Search Extensions for JIRA Cloud - soon also for the server! 

            All the features are presented in the reference manual https://jqlsearchextensions.atlassian.net/wiki/display/SEARCH/JQL+Reference . Just install and enjoy the free trial! Hi! This and many more JQL keywords are supported after installing our plugin. Make sure to check out the JQL Search Extensions for JIRA Cloud - soon also for the server! 

            Daniel Turczanski added a comment - Hi! Many more epic related JQL keywords are supported after installing our plugin. Make sure to check out the  JQL Search Extensions for JIRA Cloud  - soon also for the server!  All the features are presented in the reference manual https://jqlsearchextensions.atlassian.net/wiki/display/SEARCH/JQL+Reference  . Just install and enjoy the free trial ! Hi! This and many more JQL keywords are supported after installing our plugin. Make sure to check out the  JQL Search Extensions for JIRA Cloud  - soon also for the server! 

            Graze Atlassian Admin added a comment - - edited

            dmeyer - This is excellent. Just one bug that is really holding me up using this.

            I find it really useful to group/relate epics together using issue links (for example, to assign epics to a particular team etc.). I'd really like to find all issues/sub-tasks in a set of epics. So I expected this to work:

            parentEpic IN linkedIssues(JRACLOUD-59181)

            But at the moment that JQL returns a server error. Can that be fixed to complete this feature?

            Graze Atlassian Admin added a comment - - edited dmeyer - This is excellent. Just one bug that is really holding me up using this. I find it really useful to group/relate epics together using issue links (for example, to assign epics to a particular team etc.). I'd really like to find all issues/sub-tasks in a set of epics. So I expected this to work: parentEpic IN linkedIssues( JRACLOUD-59181 ) But at the moment that JQL returns a server error. Can that be fixed to complete this feature?

            Dave Meyer added a comment -

            Hi kostantin.stambolov2110934825,

            Can you help me understand why you want to have swimlanes per epics but only show one epic on the board? I think this is a related issue: JSW-10683

            Dave

            Dave Meyer added a comment - Hi kostantin.stambolov2110934825 , Can you help me understand why you want to have swimlanes per epics but only show one epic on the board? I think this is a related issue: JSW-10683 Dave

            kostantin-stambolov added a comment -

            Hello Dave,

            I have the following case:

            A board with "Base Swimlanes on Epics" and filter like "project = JRA and parentEpic = JRA-123".

            The board appropriately returns all linked issues for the epic (in a swimlane) but the sub-tasks for the epic are left in "Issues without epics". I expect subtasks to be also in the Epic Swimlane.

            kostantin-stambolov added a comment - Hello Dave, I have the following case: A board with "Base Swimlanes on Epics" and filter like "project = JRA and parentEpic = JRA-123 ". The board appropriately returns all linked issues for the epic (in a swimlane) but the sub-tasks for the epic are left in "Issues without epics". I expect subtasks to be also in the Epic Swimlane.

            Rashmi Shastri added a comment - - edited

            Thank You Dave!

            Rashmi Shastri added a comment - - edited Thank You Dave!

            Newton Olivieri added a comment -

            Time to update a few filters/dashboards! Great work! Thank you!

            Newton Olivieri added a comment - Time to update a few filters/dashboards! Great work! Thank you!

            Neil OHara added a comment -

            Thanks Dave, I just used this in Cloud and it's definitely nice  hopefully it's in server soon as we're moving to local server soon and I'd hate to lose a needed feature.

            Neil OHara added a comment - Thanks Dave, I just used this in Cloud and it's definitely nice  hopefully it's in server soon as we're moving to local server soon and I'd hate to lose a needed feature.

            Dave Meyer added a comment -

            Hi everyone,

            We have recently added support for this in JIRA Cloud with the release of a new JQL function called parentEpic. Searching with parentEpic will return all the issues in the specified epic(s) AND their sub-tasks. The syntax is a little bit different than a standard JQL functions – it's more like searching with a field. So

            project = JRA and parentEpic = JRA-123

            will return all issues and sub-tasks in the JRA project that are in the JRA-123 epic. The function also supports the != , IN , and NOT IN operators. So you could also search something like

            project = JRA and parentEpic in (JRA-123, JRA-456)

            and you will get all issues and sub-tasks in either the JRA-123 or JRA-456 epics.

            Refer to the documentation for more information. Happy searching!

            Note: Currently we don't have a timeline on when this will be released in JIRA Server; however we will provide an update once we do.

            Dave Meyer
            Senior Product Manager, JIRA

            Dave Meyer added a comment - Hi everyone, We have recently added support for this in JIRA Cloud with the release of a new JQL function called parentEpic . Searching with parentEpic will return all the issues in the specified epic(s) AND their sub-tasks. The syntax is a little bit different than a standard JQL functions – it's more like searching with a field. So project = JRA and parentEpic = JRA-123 will return all issues and sub-tasks in the JRA project that are in the JRA-123 epic. The function also supports the != , IN , and NOT IN operators. So you could also search something like project = JRA and parentEpic in ( JRA-123 , JRA-456 ) and you will get all issues and sub-tasks in either the JRA-123 or JRA-456 epics. Refer to the documentation for more information . Happy searching! Note : Currently we don't have a timeline on when this will be released in JIRA Server; however we will provide an update once we do. Dave Meyer Senior Product Manager, JIRA

              Unassigned Unassigned
              dsantos Daniel Santos (Inactive)
              Votes:
              208 Vote for this issue
              Watchers:
              124 Start watching this issue

                Created:
                Updated:
                Resolved: