ErrataDesign » History » Revision 4
« Previous |
Revision 4/10
(diff)
| Next »
Kyle Baker, 12/04/2014 09:37 AM
Errata Management¶
Summary¶
Errata Management should be improved so that a user can know when new errata have been brought down, and can view the relationship between errata and hosts. Errata Notifications should be simplified so that customers recieve fewer coarse grained emails, rather then more fine grained emails.
For these requirements we use these definitions:- Applicable: An errata will be applied if the host runs yum update
- Available: An errata has been synced, but not promoted to where a host can consume it
- Present: An errata has been synced, but would never be applied to a host by yum update.
Targeted Release¶
Foreman 1.8 / Katello 2.2
Trackers¶
--
Targeted Persona¶
System Engineer
Status¶
User Stories¶
Owner - David Caplan
Status - Finished
Blockers - None
Requirements¶
Owner - Mike Mccune / David Caplan
Status - Done
Blockers - None
Wireframes¶
Owner - Kyle Baker
Status - Done
Blockers - None
Last updated 10/29/2014 - https://dl.dropboxusercontent.com/u/5892944/Errata%20Management-2014-10-29.pdf
Development Stories¶
Owner - Walden Raines
Status - In Progress
Expected Delivery - TBD
Blockers - None
Documentation¶
User Stories¶
- Please include a story describing how the user would transverse this feature including the workflow. This story ideally would include what their actions would be before and after completion of the task.
Requirements¶
- User stories will be broken down of the into specific actionable tasks to design and develop against.
Development Tasks¶
- Errata Management:
- Errata Management Email Notifications
- Errata Management Environment/Content Views
- Errata Management Errata View
- Errata Management Host View
- Email Features:
Impacted¶
Future Requirements (specifically not in)¶
More Information¶
Updated by Kyle Baker almost 10 years ago · 10 revisions