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

Using the JQL sprint in openSprints() doesn't include team-managed (formerly next-gen) subtasks

      Issue Summary

      When using subtasks in a team-managed (formerly next-gen) project, those won't appear in the project issue when using the 'sprint in openSprints()' JQL operation.

       

      Steps to Reproduce

      1. Create a team-managed (formerly next-gen) project
      2. Create a few issues with subtasks in the project
      3. Go to the issue list view (PIN) and use the 'sprint in openSprints()' JQL operation

      Expected Results

      Subtasks should show in the list of issues.

      Actual Results

      Subtasks are not appearing in the list.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JRACLOUD-90892] Using the JQL sprint in openSprints() doesn't include team-managed (formerly next-gen) subtasks

            Atlassian Update - September 2023

            After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-81069 – Unable to search for sub tasks in a sprint on a team-managed (formerly next-gen) project which has more votes.

            We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - September 2023 After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-81069 – Unable to search for sub tasks in a sprint on a team-managed (formerly next-gen) project which has more votes. We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Dylan added a comment -

            Hi all,

            Thank you for raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.

            To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Dylan added a comment - Hi all, Thank you for raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            This is really frustrating as my team uses subtasks as a way to manage how many points each team member has. 

            I use a tool called sumUp for Jira which relies on a jql query. When my project was in classic this worked really well. Now that I am in next gen this doesn't work at all. 

            It isn't the tool it's the jql query which doesn't work because Jira next gen has some kind of bug that doesn't allow the jql to run properly. I repeat this worked in classic. 

            JQL: project = PA AND issuetype in (subTaskIssueTypes(), Subtask, Sub-task) AND resolution = Unresolved AND Sprint = 139

            Tool: https://marketplace.atlassian.com/apps/1211625/sumup-for-jira?hosting=cloud&tab=overview 

             

             

            Mikaela Bertucci added a comment - This is really frustrating as my team uses subtasks as a way to manage how many points each team member has.  I use a tool called sumUp for Jira which relies on a jql query. When my project was in classic this worked really well. Now that I am in next gen this doesn't work at all.  It isn't the tool it's the jql query which doesn't work because Jira next gen has some kind of bug that doesn't allow the jql to run properly. I repeat this worked in classic.  JQL: project = PA AND issuetype in (subTaskIssueTypes(), Subtask, Sub-task) AND resolution = Unresolved AND Sprint = 139 Tool: https://marketplace.atlassian.com/apps/1211625/sumup-for-jira?hosting=cloud&tab=overview      

              Unassigned Unassigned
              jfemia Julien Femia (Inactive)
              Affected customers:
              22 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: