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

Status reporting incorrectly on Frontend #222

Open
glipschitz opened this issue Jan 25, 2025 · 3 comments · Fixed by #232
Open

Status reporting incorrectly on Frontend #222

glipschitz opened this issue Jan 25, 2025 · 3 comments · Fixed by #232
Labels
good first issue Good for newcomers
Milestone

Comments

@glipschitz
Copy link

Dashboard showing Operational

Image

Front end showing no issues, but the status seems to still be linked to the incident even if it's closed as fixed

Image

Image

Image

@jbrooksuk jbrooksuk added this to the v3.0 milestone Jan 26, 2025
@jbrooksuk jbrooksuk added the good first issue Good for newcomers label Jan 26, 2025
@joelbutcher
Copy link
Collaborator

@glipschitz the components that are marked as performance issues, what's the model that's reported on, is it IncidentComponent?

@glipschitz
Copy link
Author

@glipschitz the components that are marked as performance issues, what's the model that's reported on, is it IncidentComponent?

Sorry @joelbutcher I wouldn't know.
I can QA and find bugs, but I'm no developer so I would no idea what I'm looking at code wise.

@glipschitz
Copy link
Author

glipschitz commented Feb 8, 2025

This still isn't right @jbrooksuk
I have taken an Incident through a lifecycle, the front end still shows issues even though issues is marked as resolved.

Admin View
Image

Customer View
Image

Admin View of Component
Image

Customer View of Component
Image

Inside the Incident

Image

@jbrooksuk jbrooksuk reopened this Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants