Track changes in `people.json` to detect people who left
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
#1342 introduced UserActivity to identify inactive and disabled accounts. However, it does not detect if an employee leaves until the Bugzilla account gets disabled.
Based on the discussion with @marco-c and @calixteman, we should store all the employees from the people.json file in a DB and when we update the people.json, we identify people in DB who are not employees anymore.
This will help to identify the manager of the employees who leave and will unblock the following:
- #1354
- #1370
Contributor guide
No contributing guide indexed for this repository
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 tracing the existing UserActivity implementation and the code path that reads or updates people.json. Identify how employee records are currently stored in the DB and how updates are processed. Done means former employees are detected after people.json changes and their managers can be identified, unblocking #1354 and #1370.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100