Compatibility matrix
All our integrations take advantage of the third-party platform native features for the best possible user experience. Because of the differences across the features they provide and prioritization choices on our end, not all integrations provide the entire surface Echoes can take advantage of.
For the sake of transparency, this table lists all known limitations.
Feature | GitHub | GitLab | JIRA | Linear | Shortcut |
|---|---|---|---|---|---|
Automated checks for labels | ✅ | 🟡¹ | N/A³ | N/A | N/A |
✅ | ❌ | ✅ | ✅ | ❌ | |
Labels are inherited from linked issues | ✅ | ✅ | ✅ | ✅ | ✅ |
Issues are included in initiatives completion | ✅ | ✅ | ✅ | ✅ | ✅ |
Issues may contribute to recorded effort | N/A² | N/A² | ✅ | ✅ | ✅ |
Issues contribute to the Lead time "preparation" segment | N/A | N/A | ✅ | ✅ | ❌ |
¹ GitLab in its premium plan doesn't provide an API allowing us to automate this check. We provide the same behavior as a reusable pipeline job as a workaround. ² Echoes never records efforts for GitHub or GitLab issues regardless of their labels. ³ The label can be enforced in JIRA by making the "Echoes - Intent" custom field mandatory.
✅ Full support 🟡 Partial support ❌ Not implemented N/A Not applicable
Feature requests
Please reach out to [email protected] and we will prioritize the missing features (marked ❌) you need.