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.

Sign up for GitHub

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

Jump to bottom

"view" doesn't change when "catalog" is changed #1198

Open
RH-DIPF opened this issue Nov 21, 2024 · 1 comment · May be fixed by #1218
Open

"view" doesn't change when "catalog" is changed #1198

RH-DIPF opened this issue Nov 21, 2024 · 1 comment · May be fixed by #1218

Comments

@RH-DIPF
Copy link

RH-DIPF commented Nov 21, 2024

Description / Beschreibung

Changing a catalog of a project does not automatically update the list of views that are associated with that catalog.

Expected behaviour / Erwartetes Verhalten

Changing a catalog of a project automatically updates the list of views that are associated with that catalog.

Steps to reproduce / Schritte zum Reproduzieren

  1. A new project is created by a user.
  2. The user selects "catalog A" which as a view ("View A") associated with it.
  3. Then the users switches in the same project the catalog from "catalog A" to "catalog B". "catalog B" has it's own view ("View B") associated with it.
  4. But the view that the users sees never switches. He still just sees "view A" even after switching to catalog B.

Context / Kontext

If the users switches to a catalog without any views, he doesn't see any views anymore.
This is apperently an old issue #345 that was merged with an other issue #431 . But the bug from #345 was never really resolved.
@m6121 m6121 mentioned this issue Nov 22, 2024
Merged
4 tasks
@jochenklar
Copy link
Member

Hi @RH-DIPF @m6121, since views are in principle independent from catalogs, we let projects choose, which views are used in the project. This collides with the feature that views have a catalog field (which was added later) and I see that a lot of people now have the requirement that the views are more or less strictly connected to a catalog and not to the project. The same holds for tasks, but people seem to be less interested in tasks ...

We already have the feature flag PROJECT_REMOVE_VIEWS for the feature that @m6121 implemented. Maybe we should rename it to PROJECT_VIEWS_SYNC to indicate that this instance keeps the views of a project in sync with the catalog. We could also remove the possibility to choose the views freely in this case. Otherwise people could select additional views, which are then removed, when the catalog is changed or updated.

@MyPyDavid MyPyDavid linked a pull request Jan 6, 2025 that will close this issue
Open
5 tasks
MyPyDavid added a commit that referenced this issue Jan 8, 2025
@MyPyDavid
feat(project,handlers): add sync for views and tasks, #966 #1198
9065876 
Signed-off-by: David Wallace <[email protected]>
@MyPyDavid MyPyDavid linked a pull request Jan 31, 2025 that will close this issue
signal handlers for syncing of project views and tasks #1218
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

signal handlers for syncing of project views and tasks rdmorganiser/rdmo
2 participants
@jochenklar @RH-DIPF