Access Transfer upon Death Applications Table
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
### Context
To enable registry analysts (staff) to efficiently access, review, and process death transfer applications submitted by Qualified Suppliers (QS), particularly those requiring document verification and manual approval.
### User Story
As a registry analyst,
I want to access a dedicated queue of death transfer applications submitted by Qualified Suppliers (QS),
So that I can efficiently review, verify documents, and process or return submissions based on completeness and accuracy
### Business Rules
**Queue Visibility**
- Only authorized staff can access the Transfer upon Death Applications queue.
- Submissions appear in the queue only after being submitted by a QS.
**Submission Status**
- Each submission must have a status: Draft, In Review, Approved, Rejected, or Needs More Info.
- Staff can update the status based on review outcome.
**Assignment**
- Submissions can be assigned to a specific staff member.
- A submission cannot be edited by more than one staff member at a time.
**Document Requirements**
- Required documents (e.g., Form 28, probate grant) must be uploaded by QS.
- Staff must verify document authenticity before approval.
**Audit Trail**
- All actions (view, assign, approve, reject) must be logged with timestamp and user ID.
**Security**
- Documents and submission data must be securely stored and accessible only to authorized users.
### Requirements
- Display a sortable, filterable table of submissions with columns like: Submission ID, Date Submitted, Status, Assigned To, Owner Name, Home Reg. Number, Priority, Actions.
- Staff can filter by status, assignee, date, or priority.
- Staff can sort by submission date or priority.
- Staff can open a submission to view details and uploaded documents.
- Staff can add internal notes and update status.
- Staff can assign submissions to themselves or others.
- Assigned submissions are locked for editing by others.
- Staff receive alerts for new submissions or reassigned items.
- Queue may be integrated into the existing MHR dashboard or accessed via a dedicated tab.
### Acceptance Criteria
**Scenario:** Staff views the death transfer queue
Given I am a logged-in registry analyst
When I navigate to the Transfer upon Death Applications queue
Then I should see a list of submissions with columns for ID, date, status, assignee, and priority
**Scenario:** Staff filters submissions by status
Given I am viewing the queue
When I filter by status "In Review"
Then only submissions with status "In Review" should be displayed
**Scenario:** Staff returns to the same view after closing a submission
Given I have filtered the queue
When I close a reviewed submission
Then I should return to the same filtered view
**Scenario:** Staff sees priority submissions
Given some submissions are marked as "Priority"
When I toggle the "Priority Only" view
Then only priority submissions should be shown
**Scenario:** Audit trail is maintained
Given I perform any action on a submission
Then the system should log the action with timestamp and user ID
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the existing MHR dashboard or dedicated-tab entry point and trace how submissions, staff authorization, and audit events are represented; no files or tests are named in the issue. Done means the authorized queue supports the stated columns, filters, sorting, assignment, locking, review actions, alerts, preserved views, and audit logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, frontend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100