BComp Maintenance Filings POST MVP
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
## Description:
Everything needed to complete the maintenance filings for BComp.
- COA Output -- #1539
- COD Output -- #1538 , #1416?
- AR Output -- #1665
- New functionality for AR filing (allow out of order) -- #2800
* As a (who/ person)
* I want (what/ goal)
* so that (why/ reason)
* Expected outcome:
----
* Start date when team will start to work on:
* End date Epic will be delivered:
* T-shirt size: X (S, M, L, or XL) (S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints)
* Process Flow (if applicable)
* Design/ UX or UI tasks needed (should be linked to the user stories, eventually a SPIKE or DESIGN for that Epic is needed)?
* OCM/ CM considerations?
* Architecture or data enabler stories needed?
* Possible dependencies or blockers forseen right now?
----
Enabler Epics:
* action
* result
* object
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.