Review DRS(RTR) work
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Entities role in the DRS integration review work will be to help with the following:
- System design
- Code reviews
- Helping with testing as code gets deployed to the environments
- Ensuring that DRS functionality is feature flagged and off until we are ready to go live in respective environments
**Tasks**
- [ ] Decision needed: can we use a "document generated date" instead of "document retrieval date" for modernized and legacy outputs #30416
- [ ] Test output functionality for modernized outputs
- [ ] Test output functionality for legacy outputs
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the DRS integration review tasks in this issue and clarify the decision in #30416 before beginning implementation. Review modernized and legacy output behavior in the relevant environments, verify feature flags remain off until go-live, and confirm both output test tasks are complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100