utmstack
Unable to view "tags" column in incidents - persistent loading spinner
Acknowledgements
- [x] I have searched (https://github.com/utmstack/UTMStack/issues) for past instances of this issue
- [x] I have verified that my UTMStack version is up-to-date
Describe the bug
When adding the "tags" column to the incidents view, the column header appears, but the data does not load. Instead, the classic loading spinner remains visible and continues to spin indefinitely, indicating that the view is stuck and not updating.
Regression Issue
- [ ] Select this option if this issue appears to be a regression.
Expected Behavior
The "tags" column should appear with the corresponding tags for each incident.
Current Behavior
The "tags" column header is added to the table, but no tag data is displayed. A loading spinner (the circular animated icon indicating loading) appears and continues to spin without the view ever updating or displaying the tags. This suggests that the data for the tags column is not being fetched or rendered correctly, leading to a perpetually loading state.
Reproduction Steps
- Navigate to the incidents view.
- Attempt to add the "tags" column to the displayed columns.
Possible Solution
No response
Additional Information/Context
No response
UTMStack Version
10.7.2
Operating System and version
Ubuntu 24.04.2 LTS
Hypervisor and Version | Server Vendor and Model
MS Hyper-V
Browser and version
chrome 135.0.7049.52
@robyfr Thank you for reporting this issue.
At this time, we have been unable to reproduce the described behavior in our testing environment. To facilitate further investigation, we kindly ask that you provide additional evidence. If possible, please include a screenshot or screen recording illustrating the issue.
Thank you for your time @mjabascal10!. I'm attaching a one-minute video, but more than an hour later the situation is still the same.
https://github.com/user-attachments/assets/15e4a6ce-b908-4250-b5f3-1c64bc7eb851
Thank you very much for the additional details and the video, @robyfr We’ll proceed to analyze the root cause and implement a proper solution. This fix will be included in an upcoming release.
We truly appreciate your time and collaboration.