Project

General

Profile

Bug #7338

Content view package group include filter is confusing, includes more than one group if there is overlap

Added by David Davis over 7 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
Content Views
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

1. Create a product with a zoo-lander repo (https://partha.fedorapeople.org/test-repos/zoo-lander/)
2. Create a content view with your repo and an inclusion package group filter
3. In your filter, add one package group (ie "Animal Planet") but not the other
4. Publish your view

Notice that it has two package groups and not one.

History

#1 Updated by Eric Helms over 7 years ago

  • Target version set to 55
  • Legacy Backlogs Release (now unused) set to 13
  • Difficulty set to easy
  • Triaged changed from No to Yes

#2 Updated by Walden Raines over 7 years ago

  • Status changed from New to Assigned
  • Assignee set to Walden Raines

#3 Updated by Eric Helms over 7 years ago

  • Target version changed from 55 to 56

#4 Updated by Walden Raines over 7 years ago

  • Subject changed from Content view package group filter doesn't seem to work to Content view package group include filter is confusing, includes more than one group if there is overlap
  • Status changed from Assigned to New
  • Assignee deleted (Walden Raines)
  • Target version changed from 56 to 58
  • Legacy Backlogs Release (now unused) changed from 13 to 14

This is actually working as expected. Given the package groups PG1:[1,2,3] and PG2:[3,4,5], if you include PG2 then you will get PG13 and PG2[3,4,5] after publishing. I will keep this issue open though so we can decide if we want to rework how this is handled for 2.1

#5 Updated by Eric Helms over 7 years ago

  • Target version deleted (58)

#6 Updated by Eric Helms over 7 years ago

  • Legacy Backlogs Release (now unused) changed from 14 to 23

#7 Updated by Eric Helms over 7 years ago

  • Legacy Backlogs Release (now unused) changed from 23 to 31

#8 Updated by Eric Helms over 7 years ago

  • Legacy Backlogs Release (now unused) deleted (31)

#9 Updated by Eric Helms over 6 years ago

  • Legacy Backlogs Release (now unused) set to 86

#10 Updated by Eric Helms about 6 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 143

#11 Updated by Justin Sherrill almost 6 years ago

  • Status changed from New to Rejected
  • Legacy Backlogs Release (now unused) changed from 143 to 166

This is as expected, so i'm going to close. Feel free to re-open

Also available in: Atom PDF