Project Backlog Views separated by Component?

[EX-EMPLOYEE DELETE]

The problem is that the Project Backlog is showing one future sprint section per sprint *per Component*, not one future sprint section per sprint.

Scenario: We have one project with 6 Components. We have a board that is simply the overall project board (filter is simply "Project = AC"). We have two future Sprints (named "AT Sprint 5" & 6).

The backlog view breaks up the future sprint section by component, as such:

AT Sprint 5 for Component 1

AT Sprint 6 for Component 1

AT Sprint 5 for Component 2

AT Sprint 6 for Component 2

&c &c

(the Component value is not shown on the cards but when I made it visible that's how I determined it was grouping by component

Even the "detailed issue view" appears to sort issues by Component by default.

IS there a hidden default that groups issues by component around future sprints? Is there a way to change / eliminate that default if so?

[Trudy Claspill · Accepted solution]

Hello @EX-EMPLOYEE DELETE 

That is not typically how the Scrum backlog screen displays information (Sprints sections for different components) in a Classic Software project.

Please confirm that you have not accidentally created two sprints with identical names. Jira does not prevent that from being done, so that may be what has actually happened.

You can check this by navigating the the Advanced Search screen and starting to create a filter in JQL like

sprint = "AT Sprint 5

If there is more than one sprint with that name, you will be shown multiple matching sprints, as Jira looks for sprint names matching what you have entered. That will be an indication that you have created more than one sprint with the same name.

Also, your image is not supporting your claim that the sprints are being broken into sections based on components. The one sprint you have shown has issues with two different components, and one with no component at all.

[EX-EMPLOYEE DELETE]

Complete fubar on my scrum master's part. As it turns out he didn't tell me that he created one sprint per "board" within that project - with identical names! So @Trudy Claspill thank you for the quick response. 

So there is no issue, there is nothing to see here. Jira Cloud FAD!!