Sprint lanes show up empty ( Easy Agile User Story Maps for Jira)

[Deleted user]

I have an issue with the latest upgrade.

The issues aren't shown in their respective sprints when using the sprint swimlanes. The sprints created in the backlog are shown on the board, but without issues in them. All issues are in the unscheduled swimlane

When I go to the (jira agile)backlog, the issues are visible in the correct sprints.

Am I missing some configuration? I did a reindexing to be sure, but no result

Screenshots:

[Seamus Kieran · Accepted solution]

Hi Kevin,

This is definitely not the intended function and we have a couple of working theories on what may be causing this behaviour. Can you please reach out to us at support@easyagile.com with your troubleshooting information so that I can investigate further?

This is likely due to a combination of your field configurations, and a change in the way we use the Jira REST API to detect sprints in recent versions.

Thanks Kevin.

Kind Regards,
Seamus Kieran
Easy Agile Support Team

[Deleted user]

Taking this up with support. I will leave feedback here when the solution is found. 

[Dave Elkan]

The solution to this issue was the identification of a duplicate sprint field. This issue can sometimes be the result of a Jira instance which has seen many upgrades over the years.

[Bharath Badri]

Epics i created using Easy agile are in JIRA but missing in the User story map section. How do i get them back?

[Andy Nguyen]

Hey Kevin,

I would take a look at the following menus in Board Configuration and ensure they're all right:

1. Board filter query
2. Columns
3. Swimlanes

Apart from that, I notice you tagged Easy Agile User Story Maps for Jira. May this have anything to do with the add-on e.g. is it up to date and compatible, does it need to be reconfigured upon upgrade? 

A screenshot highlighting what the problem looks like would be useful.

Cheers,

Andy

[Deleted user]

The basic atlassian jira boards are looking fine. It's related to the add-on.

[Andy Nguyen]

Thanks Kevin,

It seems you're now working further on this with Easy Agile Support Team (as per Seamus's suggestion). If so, would you mind marking his answer as the right one so that other users are aware of how to proceed when encountering this same scenario?

Cheers,

Andy