nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Backlog empty on Scrum board

unknown

I have recently installed JIRA 5.1.7 and GreenHopper 6.0.6 to review the recent changes to the boards. However, I am being faced with an empty backlog even though the project has a number of sample issues created during the project creation step.

The message visible in the backlog is "There are currently no issues in the backlog"

I have checked the filter and it appears ok. What else could be causing this to happen?

Accepted answers

unknown

The following KB has been created which rectifies the issue:

https://confluence.atlassian.com/display/GHKB/Empty+Backlog+Even+Though+Issue+Exist

All comments

John Chin

Hi Alan,

Perhaps, the message is display wrongly. For more information, you may refer to this improvement ticket GHS-6427. I suggest to vote on it and add yourself in the watch list to keep you updated in future.

Good luck.

Regards,

John

sclowes

Hi Alan,

Please check the following:

The issues your filter matches must be in a status which is mapped to a column on the board (and not the last column which is considered 'Done')
The issues aren't in an active sprint (in which case they will be in Work mode)
You don't have any quick filters active

If you find the problem is the first one (i.e. the statuses) please let us know because you should get a warning about this in the Filter section of the configuration for the board.

Thanks,
Shaun

unknown

The filter matches issues which map to columns on the board - this is visible when I go into the 'Configure' screen for the board as each column has a number of issues attributed to it.

There are no sprints configured yet, however if I configure a sprint, it makes no difference. The Backlog section in the Plan screen continues to show "There are currently no issues in the backlog".

Any ideas?

sclowes

Very weird, I'd suggest logging an issue with support at https://support.atlassian.com, they can help diagnose what's going on.

Thanks,
Shaun

C_Faysal _CFcon_

do you have Epics enabled in Greenhopper Labs?

i was facing the same problem...the epic sidebar on greenhopper view had an unlabeled epic highlighted wich causes an empty backlog view cause none of the existing issues were grouped among it

unknown

Thanks, but I've just posted the fix for my problem, was a weird data issue with the custom fields.

unknown

The following KB has been created which rectifies the issue:

https://confluence.atlassian.com/display/GHKB/Empty+Backlog+Even+Though+Issue+Exist

aaron n

Per the second resolution at the very bottom of this article

https://confluence.atlassian.com/display/GHKB/Your+issue+XXX+has+been+created+but+is+not+currently+visible+on+the+Rapid+Board

go to Administration -> Issues -> Fields

then scroll down the custom fields till you get "Sprint" field used by Greenhopper.

Check to see that it has been applied to your project, or that it is set to apply to all projects

by using the "Global" setting

aaron n

Per the second resolution at the very bottom of this article

https://confluence.atlassian.com/display/GHKB/Your+issue+XXX+has+been+created+but+is+not+currently+visible+on+the+Rapid+Board

go to Administration -> Issues -> Fields

then scroll down the custom fields till you get "Sprint" field used by Greenhopper.

Check to see that it has been applied to your project, or that it is set to apply to all projects

by using the "Global" setting

unknown

That was already suggested by the support staff, but didn't help in this situation. The KB article I posted solved this problem.

aaron n

@alan, well it was definately the problem for me. clearly if your project's issues do not have the 'sprint' field which is used by greenhopper then it won't work, regardless of what else may be wrong. btw, i re-indexed and then i think i recreated the board afterwards to get it to pick up the new field, not 100% sure on the necessity of that lest step though.

unknown

My projects did have the sprint field used by GreenHopper and still didn't work. That was the problem which this topic is about and which the KB marked as the answer solves.

Marius Vikdal

I recently had the same issue in JIRA v6.1 and Agile v6.3.1.

The solution for me was to fix the mis-match in column mapping between the different workflows.

If you go to: Board -> Configure -> Columns and check if you have any issue statuses unmapped. Drag them to one of the predefines statuses, and you should be ok.

Roxanna Maynard1

Thank you - this was the correct answer for me. Have read about 20 threads, so very happy to finally have the answer. Very helpful.

Marius Vikdal

Glad I could help

Thomas Heard1

This was my issue and fixed my problem immediately.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

board