Work item start/due date inheritance v2
Summary
Start and Due dates have been introduced for work items. In this issue, we should design the user/workflow experience related to the inheritance model whereby epics receive the start and end date values of its children.
Reference
This video walks through how the dates currently behave.
Opportunities for Improvement
- With the work items implementation, the date inheritance logic should include the issue
iteration
anddue date
.- Noting that when more than one date value is available on a record (eg. an issue with both milestone and iteration), we should take the smallest or minimum start and end values. Example: An issue has both Milestone =
May 1 - May 31
and Iteration =May 15 - May 21
. We should useMay 15 - May 21
as the value passed to the parent.
- Noting that when more than one date value is available on a record (eg. an issue with both milestone and iteration), we should take the smallest or minimum start and end values. Example: An issue has both Milestone =
- We've received feedback from a large financial customer that the term
inheritance
is not only unintuitive but it's factually incorrect. When something is inherited, it comes from a "parent" or entity above oneself. Since we are passing values from the children to the parent, users are confused by this term. - We intend to create the ability to track planned vs. actual dates in the future via #231511. This should be taken into consideration as we design inheritance for work items.
- Please review the prior UX exploration on this topic in #366245 and #389446.
Edited by Amanda Rueda