-
Suggestion
-
Resolution: Unresolved
-
None
-
4
-
Provide an option to pin Data residency of Compass similar to Jira and other products.
- is addressed by
-
ENT-2674 Loading...
- COMPASS-58Support for Data Residency
- COMPASS-138Enable Compass to support integration with GitLab on-premise instances that require proxy configuration
- COMPASS-155Compass Alerts shareable links between Members of the same instance
- COMPASS-151Support multiple visualization views to better accommodate complex architectures
- COMPASS-152Support for Infrastructure Dependency Visualization in Compass
- COMPASS-153Confluence integration
- COMPASS-84Ability to create a custom read-only role in Compass
- COMPASS-91Aggregated Metrics View for Team Components in Compass
- COMPASS-148Include Customer usage Analytics for Compass
- COMPASS-149Feature to Export site data back up and restore to Compass
- COMPASS-150Add Support for Working Hours-Based PR Cycle Time Metrics in Compass (Developer Dashboard Experience)
- COMPASS-144Customers requesting Service Resource API support using Terraform in Compass
- COMPASS-141Consider changing Deployment Frequency calculations
- COMPASS-140Ability for Compass to manage GitHub - Jira Issues
- COMPASS-95Please develop a dedicated Mobile app for Compass Operation alerts, which does not require a JSM license to use.
- COMPASS-89Add GitLab support for templates
- COMPASS-101Support for Gitlab Dedicated/Self hosted
- COMPASS-24Support for Monorepos in Compass
- COMPASS-133Integration support for Jenkins with Compass
- COMPASS-127Request for 2LO OAuth for Compass APIs
- COMPASS-27Support root org token for GitLab auth
- COMPASS-70Add support for more Component types in Grapqhl API query (Component creation)
- COMPASS-137Allow discovery and management of components within repositories with multiple levels of nested directories for SelfHosted SCM Platform
- COMPASS-13Integration between Compass and Bitbucket Data Center
- COMPASS-14Enable cross-site use of Compass + JSW
- COMPASS-21Ability to auto-connect and identify components in Statuspage
- COMPASS-37Map the deployment event name in Compass using the same configuration of Jira
- COMPASS-114App/Tools to integrate Backstage.io with Compass
- COMPASS-106Ability to send annoucement notifications to Slack/MS Teams
- COMPASS-72Enhance Flexibility of Compass Component Overview Area
- COMPASS-48Allow exporting of component lists with all or selected fields based on display to excel or CSV
- COMPASS-82Ability to save a custom view over which columns are visible in the component view.
- COMPASS-10Include pagination to the Teams page in Compass
- COMPASS-28Read-only user access
- COMPASS-46Ability to bulk edit custom fields via UI
- COMPASS-103Request for Terraform provider for Compass
- COMPASS-128Ability to set specific API Token Scope for Compass endpoints
- COMPASS-86Capability to add JSM on-call links to Compass component on-call sections.
- COMPASS-125Admin Control Over Contact Methods and Do Not Disturb Settings
- COMPASS-32User Activity Audit Log for Compass
- COMPASS-6IP allowlist
- COMPASS-97Ability to have a custom dependency tracker that isn't limited to a specific package type
- COMPASS-61Add support for custom component types in Gitlab Forge App Importer
- COMPASS-62Display custom component type in Jira Software
- COMPASS-38Ability to mass import select field options via CSV import
- COMPASS-71Ability to turn off/disable notifications when new components are created
- COMPASS-75Capability to prevent or reject component creation or import if a duplicate name already exists.
- COMPASS-85Support depends_on relationship in the CSV importer
- COMPASS-134Integration support for Datadog with Compass
- COMPASS-69Ability to add Compass Business Stakeholders
1 of 113
Support for Data Residency
-
Unassigned
-
Jonathan Andrew
- Votes:
-
15 Vote for this issue
- Watchers:
-
15 Start watching this issue
- Created:
- Updated: