Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-18760

JQL to list out the issue that are in board or in backlog for team-managed (formerly next-gen) project

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • next-gen
    • None
    • 2
    • 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.

      It would be great if we have separate JQL to list out issue that are in backlog or on board.

      This will also help in creating dashboard.

            [JSWCLOUD-18760] JQL to list out the issue that are in board or in backlog for team-managed (formerly next-gen) project

            Atlassian Update - January 2024

            After some analysis, we've found that this ticket is a duplicate of the request JSWCLOUD-20433 – Ability to search for issues in a team-managed project's backlog e.g status = backlog 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 - January 2024 After some analysis, we've found that this ticket is a duplicate of the request JSWCLOUD-20433 – Ability to search for issues in a team-managed project's backlog e.g status = backlog 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.

            I had hoped this would be addressed by AUTO-605 as it was in the issue description, but was not addressed there. Adding a searchable data marker would help with filters & dashboards if I could identify issues that were on the board vs. backlog so that I could exclude one or the other.

            Saybo Seybold added a comment - I had hoped this would be addressed by  AUTO-605 as it was in the issue description, but was not addressed there. Adding a searchable data marker would help with filters & dashboards if I could identify issues that were on the board vs. backlog so that I could exclude one or the other.

            Juha Sadeharju added a comment - Related https://jira.atlassian.com/browse/AUTO-605 .

            I initially posted my rant to JSWCLOUD-17786 but it seems that this is the main issue, so reposting also here. 

            The current implementation is broken and I really can't see why any dev would think it behaves as intended. The only way you can see whether an issue is on the board or in the backlog is by going to the board view and manually searching for the issue there. This is so impractical, annoying, and makes no sense. 

            Since there's no way to query this information, it also prevents the effective use of Dashboard filters and board & backlog automation.

            I have non-technical users that I'm onboarding to the concept of Kanban and Jira. This annoying little bug turns the simple concepts of having a Backlog and a Board into a circus of let's-find-my-issue!  Some of my users are utterly confused as to why their issues are In Progress, but not visible on their Board (which I've told them contains all the issues they should progress), because of course people will change an issue's status wherever the UI allows it, whether in the backlog or wherever.  And I can't even catch & automate these situations because the information is not available with JQL! 🙄

            This should be treated as a bug. 

            It seems that the Jira Software Cloud API allows you to query for issues from a next-gen backlog, which I've verified to work (software project, team-managed). If Atlassian is not willing, a 3rd party developer would probably be able to create a suitable workaround e.g. with a custom JQL function.

            Juha Sadeharju added a comment - I initially posted my rant to JSWCLOUD-17786 but it seems that this is the main issue, so reposting also here.  The current implementation is broken and I really can't see why any dev would think it behaves as intended. The only way you can see whether an issue is on the board or in the backlog is by going to the board view and manually searching for the issue there. This is so impractical, annoying, and makes no sense.  Since there's no way to query this information, it also prevents the effective use of Dashboard filters and board & backlog automation. I have non-technical users that I'm onboarding to the concept of Kanban and Jira. This annoying little bug turns the simple concepts of having a Backlog and a Board into a circus of let's-find-my-issue!  Some of my users are utterly confused as to why their issues are In Progress, but not visible on their Board (which I've told them contains all the issues they should progress), because of course people will change an issue's status wherever the UI allows it, whether in the backlog or wherever.  And I can't even catch & automate these situations because the information is not available with JQL! 🙄 This should be treated as a bug.  It seems that the Jira Software Cloud API allows you to query for issues from a next-gen backlog, which I've verified to work (software project, team-managed). If Atlassian is not willing, a 3rd party developer would probably be able to create a suitable workaround e.g. with a custom JQL function.

            Taylor H. added a comment -

            This is a huge oversight on next-gen, kanban style projects. Without this I feel the power of automation, tracking, etc is very limited

            Taylor H. added a comment - This is a huge oversight on next-gen, kanban style projects. Without this I feel the power of automation, tracking, etc is very limited

            Joshua Eby added a comment -

            I would love to be able to use JQL and create a filter that only returns issues that are on our Kanban board or only issues that are not on the board.  There doesn't appear to be anyway to do this.  If you are using scrum, you can look by sprint, but that doesn't create a very dynamic filter.

            Joshua Eby added a comment - I would love to be able to use JQL and create a filter that only returns issues that are on our Kanban board or only issues that are not on the board.  There doesn't appear to be anyway to do this.  If you are using scrum, you can look by sprint, but that doesn't create a very dynamic filter.

            Mark Price added a comment -

            I submitted a support request for the same issue - https://community.atlassian.com/t5/Next-gen-questions/Next-Gen-search-results-do-not-indicate-if-issue-is-on-board-or/qaq-p/1332556

            There are a number of other requests asking for the same thing, for example:
            https://jira.atlassian.com/browse/JSWCLOUD-17786
            https://jira.atlassian.com/browse/JSWCLOUD-17445

            I'm sure I can find more if I search enough.  It seems like we just need a status of "Backlog" so that all the other board statuses actually mean it is on the board, and can be searched/filtered/modified.  Can this be bumped up, it is really impacting productivity and results in the team not seeing issues on the board even through they think they should because the status is one of the board column statuses.

            Mark Price added a comment - I submitted a support request for the same issue -  https://community.atlassian.com/t5/Next-gen-questions/Next-Gen-search-results-do-not-indicate-if-issue-is-on-board-or/qaq-p/1332556 There are a number of other requests asking for the same thing, for example: https://jira.atlassian.com/browse/JSWCLOUD-17786 https://jira.atlassian.com/browse/JSWCLOUD-17445 I'm sure I can find more if I search enough.  It seems like we just need a status of "Backlog" so that all the other board statuses actually mean it is on the board, and can be searched/filtered/modified.  Can this be bumped up, it is really impacting productivity and results in the team not seeing issues on the board even through they think they should because the status is one of the board column statuses.

              Unassigned Unassigned
              dbargal@atlassian.com Darshan Bargal (Inactive)
              Votes:
              35 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: