- Epic issues API
- Milestone dates integration
- Epics pagination
- List epics for a group
- Single epic
- New epic
- Update epic
- Delete epic
- Create a to-do item
Epics API
- Introduced in Single-level Epics
Every API call to epic must be authenticated.
If a user is not a member of a private group, a GET request on that group results in a 404 status code.
If epics feature is not available a 403 status code is returned.
Epic issues API
The epic issues API allows you to interact with issues associated with an epic.
Milestone dates integration
Because start date and due date can be dynamically sourced from related issue milestones,
additional fields are shown when user has edit permission. These include two boolean
fields By default, Read more on pagination.
Gets all epics of the requested group and its subgroups.
start_date_is_fixed and due_date_is_fixed, and four date fields start_date_fixed,
start_date_from_inherited_source, due_date_fixed and due_date_from_inherited_source.
end_date has been deprecated in favor of due_date.
start_date_from_milestones has been deprecated in favor of start_date_from_inherited_source
due_date_from_milestones has been deprecated in favor of due_date_from_inherited_source
Epics pagination
GET requests return 20 results at a time because the API results
are paginated.
references.relative is relative to the group that the epic is being requested from. When an epic
is fetched from its origin group, the relative format is the same as the short format.
When an epic is requested across groups, the relative format is expected to be the same as the full format.List epics for a group
parent_iid and _links[parent] in response were
GET /groups/:id/epics
GET /groups/:id/epics?author_id=5
GET /groups/:id/epics?labels=bug,reproduced
GET /groups/:id/epics?state=opened