Why Issues in Next Gen Projects Backlog are Qualified as "To Do"?

[Stuart Scott]

Why Issues in Next Gen Projects Backlog Qualified as "To Do", this makes it impossible to use filters or create dashboards that only show items that are really "To Do" or "In progress". I don't want my team focusing on the backlog only on what really is coming up.

[Callum Carlile _Automation Consultants_]

Hi @Stuart Scott , welcome to the Community!

If you are using a Scrum project, then any issue which is created without giving it a Sprint value will be added to the backlog, as it won't be added to the current Sprint.

As soon as the issues are created, they will go into the first status of the Workflow - in your case, it sounds like this is To Do.

If you are wanting to isolate the issues which are in the To Do status but are NOT in the backlog, then you could use the JQL of project = ABC AND status = "To Do" AND Sprint is not empty, (where ABC is your project key). These tasks will not be on the backlog, as they will have been given a sprint value associated with it.