Bug 1410616 - [RFE] Prominent notification of expiring subscriptions.
Summary: [RFE] Prominent notification of expiring subscriptions.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.2.6
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: 6.8.0
Assignee: satellite6-bugs
QA Contact: Cole Higgins
URL:
Whiteboard:
: 1180160 1212064 1238223 (view as bug list)
Depends On:
Blocks: sat61-release-notes CEE_Sat6_Top_BZs, GSS_Sat6_Top_Bugs
TreeView+ depends on / blocked
 
Reported: 2017-01-05 22:26 UTC by Rich Jerrido
Modified: 2023-10-06 17:35 UTC (History)
26 users (show)

Fixed In Version: tfm-rubygem-katello-3.16.0-0
Doc Type: Enhancement
Doc Text:
You can configure Satellite to send you email notifications about subscriptions that expire in 7, 30, 60, 90, or 120 days. You can also choose how often to send these notifications - daily, weekly, or monthly. To do this, in the Satellite web UI, in the upper-right corner, click your user name > My Account, click the *Email Preferences* tab, and configure the *Subscriptions expiring soon* notification. Each user can only get information about the subscriptions that they have permission to view. + The *Entitlement* report template has been renamed to *Subscription - Entitlement Report*. In this report template, the `Name` dictionary has been renamed to `Host Name`.
Clone Of:
Environment:
Last Closed: 2020-10-27 12:57:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-6944 0 None None None 2021-12-10 15:15:19 UTC
Red Hat Knowledge Base (Article) 477863 0 None None None 2017-10-03 13:16:29 UTC
Red Hat Knowledge Base (Solution) 11025 0 None None None 2017-10-03 13:15:45 UTC
Red Hat Knowledge Base (Solution) 2050353 0 None None None 2018-07-05 15:36:12 UTC
Red Hat Knowledge Base (Solution) 2212651 0 None None None 2017-10-03 13:12:08 UTC
Red Hat Knowledge Base (Solution) 2332731 0 None None None 2017-10-03 13:12:26 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 12:57:53 UTC

Description Rich Jerrido 2017-01-05 22:26:26 UTC
Description of problem:


As a user of Red Hat subscriptions with Satellite 6, I would like the ability to be prominently notified when (large groups of) subscriptions expire. 


As I may  want to export the current state of my systems & associated subscriptions (such as via hammer csv), knowing that I have subscriptions expiring is key. 

This RFE requests:

- some form of UI notification (above and beyond the widget on the dash board)
- a new email report (such as the ones for errata) that the user can opt-in to receiving.

Comment 2 Kathryn Dixon 2017-01-06 00:53:29 UTC
see also https://bugzilla.redhat.com/show_bug.cgi?id=1238223

Comment 3 Stephen Benjamin 2017-01-09 14:33:51 UTC
Created redmine issue http://projects.theforeman.org/issues/17983 from this bug

Comment 8 Bryan Kearney 2017-12-11 17:29:44 UTC
*** Bug 1180160 has been marked as a duplicate of this bug. ***

Comment 9 Bryan Kearney 2018-03-19 16:52:57 UTC
*** Bug 1212064 has been marked as a duplicate of this bug. ***

Comment 10 Bryan Kearney 2018-07-05 15:36:12 UTC
*** Bug 1282333 has been marked as a duplicate of this bug. ***

Comment 11 Bryan Kearney 2018-07-05 15:37:26 UTC
*** Bug 1238223 has been marked as a duplicate of this bug. ***

Comment 17 Marek Hulan 2019-11-05 14:44:50 UTC
I spoke with Rich to agree on more concrete specification. Here are the stories:

As a user, I want to be able to opt-in for email notification about subscriptions expiring $soon.
Each user can only get information about subscriptions they have permission to view
As a user, I want to chose how often the notification should be sent, daily/weekly/mothly (consistent with other notifications)
As a user, I want to chose what $soon means, typically a week, 30 days, 90 days
The notification should contain the list of subscriptions, not the systems that are affected by it (attached to them).
The notification should contain the link to render a report with more details, specifically about what systems (hosts) will be affected by that expiration
As a user, I want to be able to generate Entitlements report (introduced in 6.7) and filter on subscriptions and subscription expiration date
The notification is not sent if no expiring subscription is found

The email notification will contain following information about expiring subscriptions:
subscription name, satellite organization, type, quantity, SKU, contract, account, start, end (expiry)

Comment 22 Matt Werner 2020-07-06 13:52:24 UTC
Added release note text.

Comment 24 Lukáš Hellebrandt 2020-07-30 10:27:21 UTC
This fix caused the following change: In the "Subscription - Entitlement Report" report, the "Name" column has been changed to "Host Name" column. This should be mentioned in the Doc Text.

Comment 25 Sergei Petrosian 2020-07-30 13:31:25 UTC
Hi Lukáš,

Thank you for this notice. So this "Subscription - Entitlement Report" report has been added in a past release. I am removing info that it is added in 6.8 from the Doc Text. 

I am adding the info about Name > Host Name renaming to the Doc text.

Please let me know if the Doc Text is correct now.

Thank you

Comment 26 Lukáš Hellebrandt 2020-07-30 13:47:02 UTC
The report has been renamed from "Entitlements" since the previous release. But I think it's clear enough as it is now.

Comment 27 Sergei Petrosian 2020-07-30 14:42:19 UTC
Thanks for this notice, Lukáš. For extra clarity, I have noted that the report has been renamed in the Doc Text.

Comment 31 errata-xmlrpc 2020-10-27 12:57:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366


Note You need to log in before you can comment on or make changes to this bug.