rubyforgood / rubyforgood/awbw
MonthlyReport only needs to belong to ProjectUser, not Project
Open
Nobody has claimed this yet.
database cleanup
not-ready
post-prod-data-import
stakeholder-question
- Dominant language
- Ruby
- Stars
- 15
- Forks
- 26
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 242
Description
Let's set Reports to belong to organization and belong to user.
Will need a rake task to update prod data to match. We've been leaving legacy fields in for a little bit first, and then submitting a pr to actually drop columns.
- unless ProjectUser is nil sometimes?
- investigate if we can remove this extra assn based on prod data
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 locating the MonthlyReport or Reports model and its current Project, organization, and user associations. Review the production data before deciding whether the extra association can be removed, then define the rake task needed to update legacy records and verify the resulting associations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100