Place requests for vault destruction in activity feed for administrators
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 823
- Forks
- 117
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 8
Description
Issue #416 explains how an administrator may process a request for destroying a vault.
However, the hidden location of the queue display makes it unlikely that an administrator naturally would find a newly queued item.
If the application could place a notification on the activity feed for administrators, then it is likely they would discover the request promptly.
As a further note, some administrators may prefer to allow users to elect to destroy vaults. If a vault is owned exclusively by a user, then it is unclear why the request must be approved.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #416 to understand how vault-destruction requests are processed, then trace the queue display and the administrator activity feed. Define whether a new activity notification should cover every destruction request and how the optional user-controlled destruction proposal affects approval; done means administrators promptly discover queued requests without relying on the hidden queue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100