Suggestion: Improving Progress Tracking & Collaboration in Discovery Admin Workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
In our organization, we actively use Discovery Admin Workspace for the following recurring activities:
- Insights for Missing Compute Resources – to identify and correct stale or missing discovery records
- Diagnostics Error Type Corrections – to analyze and remediate recurring discovery errors
These activities are continuous and often handled by multiple administrators in parallel.
Challenge Observed
When two or more people are working on the same set of recurring Discovery insights or diagnostic records, it becomes difficult to:
- Understand who is working on what
- Track progress on validation or correction
- Identify what has already been validated versus what is still pending
Since these records reappear over time, there is currently no clear traceability or ownership visibility within Discovery Admin Workspace.
Question 1: Progress Visibility
What is the recommended way to indicate work‑in‑progress on Discovery insights or diagnostics so that:
- Other admins know a record is already being reviewed or handled
- Duplicate effort is avoided when multiple people work simultaneously
Are there any OOTB features, best practices, or integrations (e.g., with tasks, notes, or states) to convey progress clearly?
Question 2: Validation & Reporting
What is the best approach to track and report on:
- How many insights/records have been validated or corrected
- How many are still open or unresolved
- Historical tracking for recurring records (trends over time)
Would this be best handled through:
- Custom fields or states
- Linking Discovery insights to tasks/incidents
- Performance Analytics / reports
- Any recommended data model or workflow approach?
Goal
The goal is to improve:
- Collaboration between Discovery admins
- Visibility into ongoing work
- Accurate reporting on Discovery health and remediation progress
Any guidance, platform capabilities, or real‑world implementation suggestions from the community would be greatly appreciated.
