Schedule: Item start dates are not validated for their relative position in hierarchy

[pwilkins]

The position of courseware items in the POC schedule tab and its hierarchy imply these items are ordered by their position. This is misleading since there is no validation that start dates conform to the implied ordering by position. This can result in unexpected item visibility to students. For example, a parent item can have a start date in the future, but a child item can have a start date in the past.

[pdpinch]

I'm not sure I follow. Do you have steps to reproduce?

---

I am mobile.

On Jan 17, 2015, at 12:57 PM, Peter Wilkins [email protected] wrote:

The position of courseware items in the POC schedule tab and its hierarchy imply these items are ordered by their position. This is misleading since there is no validation that start dates conform to the implied ordering by position. This can result in unexpected item visibility to students. For example, a parent item can have a start date in the future, but a child item can have a start date in the past.

—
Reply to this email directly or view it on GitHub.

[pwilkins]

Joe pointed this out to me, and yes, I can easily reproduce it. I don't think this is a high priority issue. More like "Be aware that ..."

[pdpinch]

@jmartis Isn't this a problem in studio as well? Or does studio automatically sort sections/chapters based on release date?