Open michaelchai-sentry opened 2 months ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-settings-projects for triage ⏲️
Might make sense to have a generic description
field. I'll keep it in the backlog as a possible onboarding ticket.
Might make sense to have a generic
description
field. I'll keep it in the backlog as a possible onboarding ticket.
Generic description would work for a the largest group of users, if it happens to be a url, shouldn't break anything.
external references https://docs.datadoghq.com/service_catalog/adding_metadata/ https://newrelic.com/blog/how-to-relic/improving-observability-with-metadata
Problem Statement
Hello team, submitting this feature request on behalf of one of our users:
Summary:
Problem Statement: Operating a large number of sentry projects (3,500), I currently lack the ability to reference/link this projects to my internal registry of services. When reviewing projects in sentry its difficult for me to know what the underlying ownership, deployments, and other information that is stored in our registry system.
Solution Brainstorm
Add a metadata/custom-data field for each project that can be updated via the UI and API. This would allow for customers to set data that is later referenced as needed. This would not be a required field, and TEXT is preferred to allow me to store either a single URI or to store json or yaml with information about the project.
Product Area
Settings - Projects
┆Issue is synchronized with this Jira Improvement by Unito