Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codeowners page throws error #80096

Open
JLuse opened this issue Oct 31, 2024 · 7 comments
Open

Codeowners page throws error #80096

JLuse opened this issue Oct 31, 2024 · 7 comments
Assignees
Labels
Product Area: Issues Sync: Jira apply to auto-create a Jira shadow ticket

Comments

@JLuse
Copy link
Contributor

JLuse commented Oct 31, 2024

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

When a customer opens a specific projects, codeowners they get the following error:
Image

Customer information in Jira

Expected Result

Codeowners to load under project settings

Actual Result

Error occurs

Product Area

Settings - Projects

Link

No response

DSN

No response

Version

No response

┆Issue is synchronized with this Jira Improvement by Unito

@JLuse JLuse added the Sync: Jira apply to auto-create a Jira shadow ticket label Oct 31, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Oct 31, 2024

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Oct 31, 2024

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

@getsantry
Copy link
Contributor

getsantry bot commented Oct 31, 2024

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

@lobsterkatie
Copy link
Member

@JLuse - Did you check our Sentry instance with the user's email to see what the error was?

@JLuse
Copy link
Contributor Author

JLuse commented Nov 1, 2024

@lobsterkatie No I couldnt find anything relevant looking for this org in discover. Even searching for my user didn't bring up encounters of the error

@JLuse
Copy link
Contributor Author

JLuse commented Nov 1, 2024

@leeandher
Copy link
Member

I was able to reproduce this and I can see the issue is a parsing error with their current codeowners file. Either way, a parsing error shouldn't crash the page, so I will dig into this and see how we can fix this for the user 👍 PRs incoming

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Product Area: Issues Sync: Jira apply to auto-create a Jira shadow ticket
Projects
Status: No status
Development

No branches or pull requests

4 participants