mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #1556] Display issue when adding a custom field #2918
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2918
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @NiceGuyIT on GitHub (Jul 7, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1556
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
When there are existing custom fields, adding another field causes the field names to not update properly. Switching to another custom field tab and then back shows the correct field names, implying the display is not updating correctly.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would like the display to accurately display the field names.
Screenshots

Initial fields before adding a new field.
Add a "third-field" and now "second-field" is shown twice.

Click on another tab and then back to the original tab to refresh the display. Now the correct field names are shown.

Additional context
I believe this is related to the grid on this screen because sorting does not work. If you add a field name that is in correct sorting order, the display is updated correctly. The "default" sorting order is Name descending, putting A's at the bottom. Adding a custom field named "aaa" will work correctly.
Note: Most of the testing was done on v0.16.0 but I did verify the fields are not updated correctly on v0.15.12.
Note 2: Sorting issue is mentioned in issue #1360.
@NiceGuyIT commented on GitHub (Jul 7, 2023):
This was caused by the Bionic Reader add-on.