This repository was archived by the owner on Mar 25, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 25, 2023. It is now read-only.
There is no automatic synchronization between the log view page and user tags #1585
Description
Description
The problem affects the preservation of log display filters in user tags. When changing the filter value in one of the sources, the second source does not automatically update the values. Only after reloading the page or logout/login.
Steps to reproduce
Way 1:
- Go to the "Log View" section
- Set one or more filters
- Ensure that requests to change the value of the user tags were successfully sent
- Go to the "Settings" section on the "User tags" tab
Way 2:
- Go to the "Settings" section on the "User tags" tab
- Make sure that there are filter tags for the "log view", otherwise create
- Change the value of one or more filters "log view"
- Make sure that requests to change the value of user tags were successfully sent
- Go to the "Log View" section
Actual result
Values for log view filters have not changed to new ones
Expected result
Values for log view filters updated
Environment
Browser:
- [ ] Chrome version XX
- [ ] Firefox version XX
- [ ] Safari version XX
- [ ] Opera version XX
- [ ] IE version XX
- [ ] Edge version XX
Others:
Connected requirement IDs
REQ_LOGS_019
Activity
fix(vm-logs): update user-tags in store after vm-logs filter updated (b…
dron8552 commentedon Feb 27, 2019
TO TEST:
REQ_LOGS_019
evgeniiamokhova commentedon Mar 1, 2019
Lack 1:
No automatic synchronization between user tags and filters in Log view page
Description: The values in filters are updated only after changing the corresponding user tags and refreshing the page
Steps:
Actual result: Values in log view filters haven't changed automatically after when user tags are changed
Expected result: Values in log view filters change automatically after when user tags are changed
dron8552 commentedon Mar 4, 2019
@bwsw @ershovaelena The problem: we store the VM-logs filters in multiple places: user-tags, session storage, and VM-logs state in ngrx-store. But is it necessary to save VM-logs filters in user-tags? If true - should we update tags when VM-logs filters were changed and update filters when user-tags were changed?