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

Show on issue if it is on board or in backlog in team-managed projects

XMLWordPrintable

    • 1
    • 3

    • 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.

      All issues in the backlog have the same status as the first column on the board. This means that when looking at an issue via the issue view (say, via a search) it is impossible to tell if a "to do" issue is in the backlog or on the board. It's also impossible to move it onto the board from the issue view, or vice versa.

      This leads to a cumbersome workflow when moving items back and forth between the board and the backlog. You have to find the issue via the board or backlog view and make the change there. 

      You should be able to see and change whether an issue is on the board or the backlog when viewing the issue directly.

            [JSWCLOUD-17786] Show on issue if it is on board or in backlog in team-managed projects

            Juha Sadeharju added a comment -

            It seems that the Jira Software Cloud API allows you to query for issues from a next-gen (team-managed) backlog. Just verified this with Postman. So I wonder if a 3rd party developer could workaround this with an add-on...  

            Juha Sadeharju added a comment - It seems that the Jira Software Cloud API allows you to query for issues from a next-gen (team-managed) backlog. Just verified this with Postman. So I wonder if a 3rd party developer could workaround this with an add-on...  

            Juha Sadeharju added a comment -

            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 Kanban 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 (of 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 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.

            Juha Sadeharju added a comment - 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 Kanban 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 (of 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 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.

            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-18760
            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-18760 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
              fba72b916a13 Adam Stein
              Votes:
              23 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: