GropiusIssue management across component boundaries

A cross-component issue management system for component-based architectures - with a GraphQL API, pluggable authentication and two-way sync to GitHub and Jira.

Get started

GraphQL API

View on GitHub

One issue, many components

Issues are attached to trackables rather than to a single repository, so a defect that spans several components stays a single issue instead of a thread of duplicates.

GraphQL all the way down

A public API for clients and an internal API for services, both code-first on Kotlin, Spring Boot and Neo4j via GraphGlue - with filtering, ordering and authorization built in.

Sync with the tools in use

The GitHub and Jira syncs run scheduled cycles in both directions, mapping titles, descriptions, comments and labels onto issue management systems teams already work in.

Authentication you can extend

A NestJS login service brokers OAuth and username/password strategies, issues the backend's access tokens, and links the accounts a user holds in each connected system.

Documented down to the source

The Kotlin API reference, the TypeScript login-service reference, both GraphQL schemas and the REST API are generated from the code on every deploy.

Runs with one command

A docker-compose setup brings up every service, the databases and the frontend - a separate testing compose file does the same for development.