Introducing the Program board in Plans!

[Eddie Meardon]

Hey @Lori Surapaneni

The Program board uses the same data as the rest of your plan, including the same start and end date fields. If you change those values in the Program board, they'll be reflected in the rest of your plan. But because it's meant for quarterly planning (at most 13 weeks of work), the idea is that it brings issues that have been tentatively scheduled into sharper focus as opposed to disrupting your plan.

Right now, you cannot create sprints from the Program board, only add existing ones from a team's board. By default, the Program board creates columns based on the schedule you configure. For example, if you set your board to be five iterations of two weeks each beginning February 1st, the first column will be Feb 1 --> Feb 14th, the next column would be the 15th to the 29th, and so on and so forth. Dragging an issue to these columns schedules it according to these dates. You can replace these dates with a teams' sprints for more accurate planning, but it's not necessary. 

[Morgan Yu]

Hi, I had some questions on once linking the proper teams & sprints to the Program Board, what is expected to show? For example A/D Sprint 29 already have tickets lined up prior done via Backlog, but none of them are reflecting? Similarly I dragged an epic into a sprint on the program board, but looking at backlog I'm not seeing that epic in the sprint either?

Sorry, am I missing something here?

[Eddie Meardon]

Hi @Morgan Yu

A few questions and thoughts: 

1. For your first question, are the issues already scheduled in the backlog assigned to the team using the Team field? This has to be explicitly configured, which might block it from showing since it doesn't know in which teams' queue to put it. 

2. For the changes made on the Program board to show on the backlog (or outside of your plan in general), you'll need to use the Unsaved changes button in the upper right. Plans is currently a sandbox, meaning that the changes you make are held here until you're ready to commit them back to the projects. You can find out more about saving changes in our documentation. 

Do these help?

Cheers

Eddie

[Morgan Yu]

Hey @Eddie Meardon 

Appreciate the response, it was the Team field that I didn't know we had to set explicitly in the ticket, I thought with the sprint itself and having assignees per ticket it will auto look at which team the assignee belongs to (I forgot a user can belong to multiple teams).

Adding that field to tickets and assignee the team value made it show up on the program board. Thank you!