Expose dueDateFromInheritedSource on epics so that inherited due date is always retrievable
Using the following query for epic due date on epic board sidebar:
query epicDueDate($fullPath: ID!, $iid: ID) {
workspace: group(fullPath: $fullPath) {
__typename
issuable: epic(iid: $iid) {
__typename
id
dueDate
dueDateIsFixed
dueDateFixed
dueDateFromMilestones
}
}
}
dueDate
takes value of dueDateFixed
when dueDateIsFixed
is true, and the value of dueDateFromMilestones
when dueDateIsFixed
is false. dueDateFixed
returns last set value by user, even when dueDateIsFixed
is false.
I'd expect dueDateFromMilestones
to always return a value when a milestone with dates is assigned to an issue under the epic, but it's null when dueDateIsFixed
is true. So here is what happens when date is fixed, even though a milestone date exists, and what I'd like to be able to do:
Current behaviour | Expected behaviour |
---|---|
To see the milestone date while Fixed
is selected, the user currently has to select Inherited
and then refresh the page. The same is probably happening with startDate
though I haven't started testing it yet.
Proposal (2021-04-29)
due_date_from_milestone
is deprecated on the REST API and to change it here would require changing at the model level and altering the REST API behavior in the process, or creating a special case for GraphQL.
Instead, we should expose due_date_from_inherited_source
as dueDateFromInheritedSource
on epics in the GraphQL API, which will always return the inherited value.
Additional proposal (2021-08-18)
Additionally expose start_date_from_inherited_source
as startDateFromInheritedSource
on epics in the GraphQL API, which will always return the inherited value.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.