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

Label "Convert to static view" does not sufficiently communicates that view will be cleared #532

Closed
ev-sc opened this issue Jan 5, 2022 · 1 comment · Fixed by #2392
Closed
Labels
🐜 bug Something isn't working 🚪 entry-level Good for newcomers

Comments

@ev-sc
Copy link
Contributor

ev-sc commented Jan 5, 2022

Description

When you click "convert to static view" from a smart view, the view is cleared - all rows are deleted.

Expected Behaviour

UI is correctly labelled and/or warns before deletion

Actual Behaviour

UI does not inform that row deletions will take place

Steps to reproduce

  1. Go to any single smart search view page
  2. Click on "convert to static view"
@ev-sc ev-sc added the 🐜 bug Something isn't working label Jan 5, 2022
@richardolsson richardolsson changed the title "Convert to static view" deletes all rows from view Label "Convert to static view" does not sufficiently communicates that view will be cleared Jan 6, 2022
@richardolsson
Copy link
Member

The easiest way to fix this (as suggested by @lowlandjuju elsewhere) would be to just change the label of this menu item, to indicate somehow that the view will be cleared as part of the "conversion".

Another option is to actually keep the content, as suggested in #533. I've explained in a comment on that issue what actually happens behind the scenes, the most important of which is this:

Turning a dynamic view into a static view means deleting the associated Smart Search query. This causes the API to start returning any statically defined rows instead. If none had previously been added, the view will be empty.

This is destructive only in the sense that the query is lost. You could attach an identical query and get back the same results as before converting, but you would have to configure that query yourself and if it was complex that might be difficult. If you do attach a query again (identical or otherwise) any people that were previously "in the view" will return as if nothing happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐜 bug Something isn't working 🚪 entry-level Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants