Welcome to the Atlassian Community!
So, my "Statler and Waldorf" instincts kicked in on this one and I think I'm going to come across as grumpy here, but why are people asking for this?
If they go to the backlog, they should be seeing the issues in the backlog. If they go to the board, they should be seeing active issues. If they search for issues in any state, then they will get a list of issues that need doing (or have been done).
For an Agile team, there's a simple argument - if it's on the board, the team are working on it, so it won't be in the backlog, so you don't need a backlog "field". For a non-Agile team, look at the status. But in both cases, ask the question - what would a backlog flag tell your teams that they can't work out from the board? And, how would an issue in the backlog end up out of the backlog and on the board while still being in the backlog?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.