Bug #23991

Even with the RSS feed disabled, community items are still present

Added by Walden Raines over 2 years ago. Updated over 2 years ago.

Target version:
Bugzilla link:


Cloned from
Description of problem:
Satellite 6.4 introduced RSS feed functionality to display community news in the notification area. The feed itself is configurable in Administer -> Settings menu, Notification tab, where it can be disabled. But even if disabled, the "Community" category is still present in the notification drawer.

Version-Release number of selected component (if applicable):
Satellite 6.4 Snap 2

How reproducible:

Steps to Reproduce:
1. Have the RSS feed enabled, and the "Community" category with a few items in the notification drawer.
2. Disable the RSS feed in Administer->Settings->Notifications
3. Check the notification drawer

Actual results:
The "Community" category still present.

Expected results:
The "Community" category disappears from the notification drawer.

Additional info:
Given some time (in order of hours), the "Community" category finally disappears. I understand that the RSS feed is checked every 12 hours, and probably the task finds that it was disabled at that time, and removes the feed from the notification drawer. Despite this, I think it will be confusing for the user, if he disables the RSS, and it is still present for a rather long time.

Associated revisions

Revision e4df3b80 (diff)
Added by Amir Fefer over 2 years ago

Fixes #23991 - rephrase RSS setting description


#1 Updated by Marek Hulán over 2 years ago

  • Priority changed from High to Normal
  • Category set to Notifications

We need to rephrase the setting description. Instead of get, we should use receive or pull as it felt like user wouldn't even see existing rss notifications.

#2 Updated by Amir Fefer over 2 years ago

  • Assignee set to Amir Fefer

#3 Updated by The Foreman Bot over 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request added

#4 Updated by Amir Fefer over 2 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#5 Updated by Walden Raines over 2 years ago

  • Triaged set to No
  • Legacy Backlogs Release (now unused) set to 330

Needed in 1.18

#6 Updated by The Foreman Bot over 2 years ago

  • Pull request added

Also available in: Atom PDF