Issues with sprint boards for next-gen projects

[Esther Strom]

This may be user error, since I'm not familiar with the next-gen projects yet. I created a demo project that I want to use a sprint board with, rather than Kanban. I turned on sprints and backlog in the project settings, and can see my backlog.

I dragged a bunch of issues up into my sprint, but every time I refresh the page, they vanish and it tells me there are zero issues in my sprint. I've done this almost a dozen times now, and it happens every time (and by refresh the page, I'm including when I close the browser window and reopen it later.) I also see no issues if I click the Board link and view the board for my sprint.

Am I missing something? (Animated gif attached.)

Edited to add: I deleted the existing sprint using the three dots menu and started over. I dragged issues up to the top, and clicked the Start Sprint button. Even though you can clearly see that I have 5 issues in the sprint before clicking Start, the modal that opens when I click the button says there are 0 issues. 

[Petter Gonçalves · Accepted solution]

Hello Esther,

I think that you are being affected by the following bug:

- Unable to add issues to sprint on Next-gen projects

Can you check if the workaround provided works for you? Here are the steps:

1. Go to the Project Settings >  Issue types and find the affected issue type.
2. Change the order of any 2 fields and click Save.
3. Revert the ordering and click Save.

We will be waiting for your answer.

[Esther Strom]

Thanks for the response. The description of the issue:

"This happens to instances that previously had turned on Sprint featured, but then turned it off again. An upgrade task ran on their instance, and then they turned Sprints back on."

Doesn't apply to our instance; we never had Sprint turned on for our next-gen projects, because this is a new cloud instance. But I tried the workaround anyway. Didn't fix the problem.

[Esther Strom]

@Petter Gonçalves - the workaround didn't work, which doesn't surprise me as the description of the issue didn't really match mine. But I did get a notice after watching that ticket that an update was run on all instances, and sprints now work correctly for me.

[Petter Gonçalves]

Hello Esther,

Thank you very much for your feedback about this.

I was investigating and noticed that the workaround described in the feature request might not work for some customers indeed, although that you confirmed that no one has turned off/on the Sprint feature of your board.

Anyway, I'm glad to know your issue is solved. Have a nice weekend!

[Adam Borries]

I have the same problem. 

1. Create sprint in recently-created next-gen project. 
2. Title of sprint is based on a different (classic) Jira project. 
3. Unable to drag issues to new sprint. 

Workaround: 

1. Rename sprint (optional?).
2. Open an issue and assign to sprint in the Sprint field. 
3. Refresh backlog view, and dragging works.