Bug 806383

Summary: [RFE] As the SE administrator I want to see all active and scheduled sync tasks for all organizations in one place
Product: Red Hat Satellite Reporter: Og Maciel <omaciel>
Component: Content ManagementAssignee: Martin Bacovsky <mbacovsk>
Status: CLOSED NEXTRELEASE QA Contact: Og Maciel <omaciel>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: bkearney, mbacovsk, mmccune, xdmoon
Target Milestone: UnspecifiedKeywords: FutureFeature, Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-08 18:42:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Og Maciel 2012-03-23 15:28:52 UTC
Description of problem:

The use case here is the administrator wants to manage all the active and currently running sync tasks from one single place in the web ui. Currently he would have to click through every single organization and from there select its sync status tab, which can be time consuming.

Another case would be to perhaps cancel a sync plan that is pegging down the SE. If we could have a "unified" view for the admin, then he/she could cancel (even manually force start) sync plans.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mike McCune 2012-09-07 21:00:16 UTC
not high enough priority to be done in 1.1, moving to 2.0

Comment 2 Pavel Pokorny 2012-09-10 07:01:00 UTC
We can discuss about how it should look in PR [1].


[1] https://github.com/Katello/katello/pull/560

Comment 3 Martin Bacovsky 2012-10-05 14:29:21 UTC
Merged in the commits: d8841b9, 5f20a24, ffbaa00

Taking the bug in case there are any dev action needed later..

Comment 4 Mike McCune 2013-09-19 18:15:33 UTC
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.

Comment 5 Mike McCune 2013-09-20 02:30:07 UTC
This bug was mistakenly closed during a triage process.  Moving back to MODIFIED or ON_QA depending

Comment 6 Bryan Kearney 2014-09-08 18:42:15 UTC
I show these prs as merged. I am closing them out. If you disgaree, please feel free to re-open.