Issue Summary

Do not show Epics or any other level 1 issue hierarchy Work type in the "Drag Issues to schedule" column in a program board

Currently, on the Program board, we see all the Work types fetched by the Work Item Sources of the Plan where the Program board is created. 

As a result, when we don't plan/schedule the issues based on Sprints on the Program board, then on the Program Board, each column represents a specific no. of weeks & each column has specific capacity. for ex: Each column may represent 2 weeks and 30 Story Points is the configured capacity for the team for those 2 weeks or that column. 

Now, in the "Drag Issues to schedule" column in a program view, we show "Epic" work types as well for scheduling. 
If you drag the Epic work item into one of the columns, you will notice that the "Story Points" estimate of that Epic Work Item is not getting considered for capacity planning in that column of the Program Board. For example, the capacity in a column of the Program Board still shows "0/30 Story Points" even though the scheduled Epic work item has 4 Story Points. 
Below is the reason for this behaviour: 

• An epic often represents a large piece of work that would be further broken down into stories/tasks. If we include epics in capacity calculation, the numbers would be duplicated. 
  For example, An Epic Work Item has 4 story points. 2 of these story points out of 4 are with a Story Work Item, and the other 2 Story Points are with a Task Work item, which are child issues of the Epic Work Item. 
  Now in the scenario where both the Task & Story work items are added & scheduled in the Program board along with the Epic Work Item, if we include the Story Points of the Epic work item in capacity calculation, then the column of the Program board will have 8 Story Points (= 4 Epic Story Points + 2 Child Task Story Points + 2 Child Story issue type's Story Points) instead of 4, although there is only 4 Story Points worth of Work Items scheduled in that column. 

However, due to the above logic, Users often get confused that why Epic Work Items are shown in the "Drag Issues to schedule" column in a program board, when they are not going to be considered for capacity planning. 

Hence, to avoid the confusion, bring improvements to not show Epic Work Items or bring a setting to allow inclusion of Epic Work Items in capacity planning while not allowing it's child issues. 

Steps to Reproduce

1. Create a Plan and add Work Item sources to include Epic Work Items on the plan. 
2. Create a Program Board on the Plan. Configure the number of weeks for each column and the capacity of each column. 
3. Do not add Sprints to the Columns of the Program board. 
4. Note that in the "Drag Issues to schedule" column, you can see the Epic Work Item.
5. Drag the Epic Work Item into one of the Columns to schedule it. 

Expected Results

Do not show Epic Work Items in the "Drag Issues to schedule" column.
Or allow inclusion of Epic Work Items in capacity planning while not allowing it's child issues. 

Actual Results

You will be able to drag the Epic Work Item into one of the Columns to schedule it but it's Story Points will not be considered for Capacity Planning of that Column on the Program board. 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available