search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.3k stars 4.21k forks source link

Azure integration doesn't currently see certain issues #77307

Open dalnoki opened 2 months ago

dalnoki commented 2 months ago

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  1. install the Azure DevOps integration
  2. try linking a certain issue - it won't appear in the list

please see the internal ticket for more information

Expected Result

the customer should be able to link the missing issues as well

Actual Result

the customer cannot currently link all issues

Product Area

Settings - Integrations

Link

No response

DSN

No response

Version

No response

┆Issue is synchronized with this Jira Improvement by Unito

getsantry[bot] commented 2 months ago

Auto-routing to @getsentry/product-owners-settings-integrations for triage ⏲️

getsantry[bot] commented 2 months ago

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

sentaur-athena commented 2 months ago

@dalnoki most of the time problems like this are caused by the alert config creating an invalid issue on the other integration. Please check to make sure fields that are set from Sentry are valid values on the Azure side. Need integration ID and org slug to be able to investigate more.

dalnoki commented 2 months ago

hi @sentaur-athena I added all the needed information to the internal Jira ticket as I mention it in the description, let me know if you need anything else to investigate!

sentaur-athena commented 2 months ago

@dalnoki we're currently in the process of updating our Azure dev ops apps since the existing app is being deprecated. We will communicate the changes with the customers on how to move from this app (which will be legacy) to the new integration. But meanwhile don't provide support unless it's an issue affecting multiple/all customers.

rodolfoBee commented 1 month ago

@sentaur-athena We got another user affected by this same issue. They have already updated the integration (on the 3rd of October). Here are the steps to reproduce as provided by the user:

  1. DevOps tickets newer than 54335 does NOT appear on the search
  2. Repro Steps

This is the same behaviour reported by @dalnoki I'm adding the internal ticket and more information from the user to the linked Jira issue. due to PII.

sentaur-athena commented 1 month ago

@rodolfoBee that's the same user and issue, just a different employee reporting it. We will look into this but issues affecting only one user unfortunately take more time to prioritize. I'll get back to you when we have updates.