## Interlock candidate - executive summary We have the REST API for Issues and Epic, but all new features(custom statuses, custom fields, etc...) are only accessible through the GraphQL API. There are also a few fundamental differences betweek work items and issues: all work items types will be available on projects in the future. Clients are very vocal about the need for the REST API, and hesitate to adopt features not accessible through it. #### Engineering Assessment * There's a clear implementation path: all operations we have exposed use Finders/Services, so both GraphQL and REST will wrap these services. * There are a few open questions about the API design, but those can answered during the implementation. * There are no dependencies on other teams #### Dependencies There are no major dependencies, only team capacity constraints. - Team dependencies: soft dependency on \~"group::api" in case they have new guidance on GraphQL/REST APIs, versioning etc... But we can also execute independently. - Epic/Issue dependencies - _None_ - External dependencies: None #### DRIs - **PM**: @gweaver <!--also add as assignee to this epic--> - **EM**: @vshushlin <!--also add as assignee to this epic--> - **UX/PDM**: @nickbrandt <!--also add as assignee to this epic--> - **Group(s)**: ~&quot;group::product planning&quot; <!--also add as label--> - **Engineering Owner**: @johnhope @nicolasdular #### Initiative Driver - Product or Engineering? - [x] **Product-driven initiatives (P1/P2/P3)** - Customer-facing features or improvements driven by Product teams that require engineering resources and commitment - These initiatives require a Product Priority label (P1/P2/P3) - They may also receive GTM tier labels (T1/T2/T3) for external communication - [ ] **Engineering-driven initiatives (E1/E2/E3)** - Internal technical improvements that may not have customer-facing components - These initiatives require an Engineering Priority label (E1/E2/E3) - They have internal visibility only and are not externally communicated - Examples include: technical debt reduction, infrastructure improvements, refactoring, dependency upgrades