App Config follow-up issues
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 17h 7m
- Merged PRs (30d)
- 358
Description
## Objective
Collect the defects and gaps found while exercising the shipped App Config API, so they are tracked apart from the delivery epic BA-5781 and can be excluded from a behaviour test run as known issues.
## Background
BA-5781 tracks building the App Config API across scopes. That work is landing; what this epic holds is what turned up afterwards - behaviour that is wrong or missing on the merged code. Keeping them here leaves BA-5781's scope intact.
## Related
- BA-5781 - App Config API (global / domain / user scopes), the delivery epic.
JIRA Issue: BA-7230
Contributor guide
Research direction
Start by reviewing the shipped App Config API work tracked under BA-5781 and the defects or gaps found after delivery. No implementation file, entry point, or test is named here; done means identifying and tracking the individual known issues separately from the delivery epic so they can be excluded from behavior tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100