Verify - BE - Not in Good Standing flag needs to be activated for one or more failed Annual Reports
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
- [ ] Check if the Good Standing flag exists and how is triggered
- [ ] The AR is due on the one year anniversary, and needs to be done within 60 days. Becomes overdue at > 60 days due.
- [ ] Valid for BEN, ULC, CCC, BC
- [ ] Follow the restrictions associated with this flag
Alerts design:
https://invis.io/T41338ZZ5GSE#/469515305_02_Multiple_Alerts
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking whether the Good Standing flag exists and what triggers it. Review the annual-report timing, entity-type coverage, associated restrictions, and the linked alerts design; done means the flag activates for one or more failed Annual Reports and follows those rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, postgres, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100