Easy Agile Programs: Team Planning iteration column doesn't allow assign an issue (gray background)

[David Leal]

It was working before with no issue, but now for some reason it doesn't allow me to grab the issue that is part of the epic to the first iteration of my Program Increment. It works if I move the epics to another iteration. That epics belong to a Kanban board (ARQ), and the iteration/sprint dates are determined by other boards that are scrum. I have this issue for this team, and for the first iteration only. This is what I have done so far with no success:

1. Remove the epic and create a new one with the same name
2. Remove the issues and create new ones with the same name
3. Remove the program increment and create a new one with the same configuration
4. Remove the program itself and create a new similar one
5. Remove the sprints from the scrum boards and create a new one with a similar name
6. Move another epic from ARQ board to first iteration and try to plan it, same situation it doesn't allow it

Here is the picture:

The gray background seems to mean, something is broken or that iteration cannot be planned for that team. If I unselect this epic, it shows the entire column with the same color:

Have you seen that before, I don't know what else to do. Thanks for any help.

[Henri Seymour {Easy Agile} · Accepted solution]

Hi David, 

Easy Agile Programs only enables you to plan current or future iterations. 

• For Scrum teams, this means Active or Future Sprints. 
• For Kanban teams, this is determined by the dates of the iteration (calculated based on the increment start date). 

Past iterations are greyed-out, as in your screenshots of a Kanban board where Sprint 1 is Feb 8-21. 

As your teams progress through a Program Increment, their progress so far will be visible in previous iterations based on what was previously scheduled. This enables teams to visualise what they've done, what work "rolled" into the following iterations, and whether the plans for the Program Increment need to be adjusted. 

Let me know if that explains the behaviour you're seeing or if you have further questions! 

Henri 

[David Leal]

Thanks @Henri Seymour {Easy Agile} it makes sense, just that it is only grayed out for my Kanban team, for the Scrum teams, the information is the same (the first iteration is in the past). I will do some tests and I confirm it. Thanks a lot!

[David Leal]

Thanks @Henri Seymour {Easy Agile} it worked, I move my sprints one year and now I an can plan iteration 1.

[Tenille _ Easy Agile]

Hi @David Leal, Henri is taking a well-earned break.

I really appreciate the update, and am glad to hear that your planning is back on track. 

Cheers,

Tenille