Background job to remove orphaned attachments
- Dominant language
- Clojure
- Stars
- 66
- Forks
- 28
- Avg merge
- 7d 4h
- Merged PRs (30d)
- 2
Description
We can have either or both of:
- A background job to remove orphaned attachments. It can be difficult to know an application is not currently worked on. This would need tracking of everyone working on applications using UI or API for completeness. Perhaps using features of #2622.
- Extend #3041 process manager to all state changes considering the application (as most actions can have comment or so at least).
Contributor guide
Research direction
Start by reviewing the features discussed in #2622 and the process manager work in #3041. Determine whether the intended outcome is orphan cleanup, tracking application activity, or extending state-change handling, and identify the relevant entry points before defining tests and completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100