TFRS - Supplemental reporting date restriction not working for compliance unit availability (In progress)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 25
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Describe the Bug
A clear and concise description of what the bug is.
Expected Behaviour
A clear and concise description of what you expected to happen.
Actual Behaviour
A clear and concise description of what actually happens.
Implications
A clear and concise description of any implications.
Steps To Reproduce
Steps to reproduce the behaviour:
User/Role:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
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
The issue body is still an unfilled bug-report template and names no files, tests, entry points, or concrete reproduction steps. First document the affected compliance-unit availability scenario and the supplemental reporting-date expectation; only then can the relevant code and a suitable regression test be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100