...
The Product team prioritized the following themes and tasks for Sprint 137 comprising 23 points. The team pulled 2 tickets into the sprint related to VA support (CONN-1292) and CI Build failure(CONN-1294) adding 3 points. Sprint status is good and the team completed 26 points this sprint. These themes included -
- Partner and Community support
- Resolution of CONN-1273 (Addressing Resolution Issue with CONN-875), Build for 4.3.2.
- Admin GUI (Testing , Cleanup Tasks)
- X12 Research (Review of WSDLs, Continued Requirements and Documentation Refinement)
The team pulled 2 tickets into the sprint related to VA support (CONN-1292) and CI Build failure(CONN-1294) adding 3 points. Sprint status is excellent and the team completed 26 points this sprint. The team provided a release tag 4.3.2-RC1 to SSA for the namespace/PurposeOfUse issue. Also the team made progress with the X12 Document Submission development for the real time transactions. The team continued supporting VA and the broader CONNECT community.
Burndown
Sprint Themes and related tickets for Sprint 137:
...
- Forum discussions
- VA 4.2.2.1 implementation
- DoD Table Update Issue
- Community and OHT support
- Minimal testing support for INHS Onboarding
- Met with Healtheway to discuss Knowledge Sharing and Vendor testing issues
- Researched Vendor testing issue provided by Healtheway for the meeting
- Support VA with 4.2.1 upgrade - AnswerNotAvailable issue(CONN-1292)
- Discussed an issue VA is seeing in the 3.2.2.1 production code base. Discussed possible troubleshooting ideas monitoring logs and explained conditions when CONNECT sends AnswerNotAvailable.
- Worked with CMS team to resolve a ws-addressing issue occurring with a particular trading partner
- Fixed SSA issue related to PurposeofUse and Role xsi:type attributes NOT scoped correctly. (CONN-1273)
- See below for snippet showing the namespaces correctly defined
...
JIRA Planning Board of Committed User Stories for Sprint 137:
Related Files
Sprint 137 code 137 code tag