Bug 2216757

Summary: CV page needs refresh to get the current filters state
Product: Red Hat Satellite Reporter: Vladimír Sedmík <vsedmik>
Component: Content ViewsAssignee: Samir Jha <sajha>
Status: VERIFIED --- QA Contact: Vladimír Sedmík <vsedmik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.14.0CC: pcreech, rlavi, sajha
Target Milestone: 6.14.0Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-katello-4.9.0.2-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vladimír Sedmík 2023-06-22 13:22:04 UTC 
Description of problem:
When adding/removing a filter to/from a content view, we need to refresh the CV page to get the current state of applied filters, otherwise later in the Publish overview modal the previous state is displayed instead of the current one.


Version-Release number of selected component (if applicable):
6.14.0 snap 4


How reproducible:
always


Steps to Reproduce:
1. Have a CV with some content.
2. Add a filter (no matter the type) and publish.
3. Remove the filter added in 2. and publish again.


Actual results:
2. No info about applied filters shown in the publish overview modal.
3. "Filters will be applied to this content view version." info is shown in the publish overview modal.


Expected results:
2. "Filters will be applied to this content view version." should be shown in the publish overview modal.
3. No info about applied filters should be shown in the publish overview modal.


Additional info:
If we refresh the CV page before publishing, the correct state is used for the message.
Comment 1 Samir Jha 2023-06-23 16:44:04 UTC 
Created redmine issue https://projects.theforeman.org/issues/36529 from this bug
Comment 3 Bryan Kearney 2023-07-06 16:03:15 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36529 has been resolved.
Comment 5 Vladimír Sedmík 2023-07-13 10:19:01 UTC 
Verified in 6.14.0 snap 7.

Steps from comment#0 provide the expected results.