Project

General

Profile

Actions
Copy link

Bug #9065

closed

incremental update should handle multiple errata and multiple content views with varrying errata needs (based on systems)

Added by Justin Sherrill about 9 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
API
Target version:
-
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

is if you select 5 errata
and for 1 of those errata, 10 differents system are applicable (in 10 different content views, for
simplicity)
but the other 4 are only applicable to 1 of the systems
we should NOT push those 4 to the other 9 Content Views

This would mean adding a flag to to restrict errata based on what is applicable

Actions
Copy link
 #1

Updated by Eric Helms about 9 years ago

  • Target version changed from 63 to 66
Actions
Copy link
 #2

Updated by Eric Helms about 9 years ago

  • Target version deleted (66)
Actions
Copy link
 #3

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release set to 114
Actions
Copy link
 #4

Updated by Justin Sherrill over 7 years ago

  • Assignee deleted (Justin Sherrill)
Actions
Copy link
 #5

Updated by John Mitsch over 4 years ago

  • Status changed from New to Rejected
  • Target version deleted (Katello Backlog)

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Actions
Copy link

Also available in: Atom PDF