In recent conversations, we discovered the need to give analysts a snapshot of useful information as soon as they log in to the registrar. Let's have more discussions around this to uncover which elements may be helpful on that initial admin landing page.
Example concepts to explore:
Total requests: Expose the number of domain requests in the queue and how many are in each status; link to filtered list for quick viewing.
899 total
820 in "submitted"
60 in "in review"
19 in "action needed"
Requests by investigator: Expose the number of requests that are assigned to each analyst and in which status; link to filtered list for quick viewing.
For Katherine
10 total
4 "in review"
3 "action needed - already has domains"
3 "action needed - unclear org eligibility"
Old requests: Expose the number of domains that are older than XX number of days; link to a filtered list of those requests.
Domains on hold: Expose the number of domains that are "on hold"; link to a filtered list of those domains.
Federal requests: Expose the number of domains that are for Federal org type; link to a filtered list of those domains.
This may not be relevant for everyone, but important for Alex and Cameron.
Election requests: Expose the number of domains that are election offices; link to a filtered list of those domains.
This may not be relevant for everyone, but important for Alex and Cameron.
Acceptance criteria
[x] Define concepts that could be added to a dashboard view
Issue description
In recent conversations, we discovered the need to give analysts a snapshot of useful information as soon as they log in to the registrar. Let's have more discussions around this to uncover which elements may be helpful on that initial admin landing page.
Example concepts to explore:
Acceptance criteria
Additional context
Miro Workshop - started 7-30-2024
Links to other issues
Loosely related to:
2238
Related to:
2418 (analysts csv... look at this for additional "wants")