Sprint 134 Progress Summary

Owned by Deepthi Rodrigues (Unlicensed)
Last updated: Jul 14, 2014
3 min read

Jun 16 - June 30, 2014

Executive Summary

Overall Status

The Product team prioritized the following themes and tasks for Sprint 134 comprising 34 points. Sprint status is fine and the team completed all the tasks for the themes this sprint .  These themes included -   

 THEME 1 – Complete Direct development from a Config services integration on all app servers and implementing the base framework for message monitoring

THEME 2- Complete consolidating look and feel for all Admin GUI pages including Direct Config GUI

THEME 3 – Continue to work with CMS to come to  a common understanding of what will be delivered and understand clearly the expectations

In addition to the rest of the themes described above the Product Team will continue its support of the community(Tiani/INHS), ongoing support for VA on their 4.2.1 upgrade, work with OHT and Healtheway product certification testing.

The team completed 19 task oriented tickets totaling 34 points this sprint. A couple of tickets were pulled out of the sprint to to account for the additional support work that was required during the sprint.

Burndown


 

Sprint Themes and related tickets for Sprint 134:

  • Community Implementation support
    • Responded to forum posts - http://www.connectopensource.org/developer-resources/forums
    • Support VA with 4.2.2.1 upgrade (CONN-1211)
      • CONNECT Development Team were assisting the VA implementation team to resolve the CONNECT 4.2.x deployment and configuration issues in the VA SQA2 & Dev environments
      • Supporting VA team few times through phone and were related to questions about DR, DS and DQ configuration setup.
      • VA team reported an time out error after receiving a DQ response from one of their partners and we suggested to fix the internalconnectioninfo and looks like that resolved the issue
      • VA team were getting an endpoint url null error on a DS outbound request and the issue was resolved by fixing the internalconnectioninfo and also the gateway.properties
    • Continued discussion with CMS on X12 support and understanding requirements (CONN-1173)
    • Supported DoD and investigated issue related to SAML Issuer.(CONN-1215)
      • The team investigated the issue and ran a few tests against the DIL and saw that 4.3 successfully passed. 
      • The team also did some additional scenarios testing related to SAML issuer and Subject Name IDs. If the proper values are provided in the Entity request, the values get propagated into the SAML headers in the NwHIN message. The issue was later attributed to a known defect in the DIL related to the sequence of the CN value in the distinguished name.
    • Follow-up with Tiani/INHS with timestamp/signature validation (CONN-1177)
      • Support involved analysis of logs and providing guidance.
  • Next Release (4.4)

JIRA Planning Board of Committed User Stories for Sprint 134:

Related Files


Sprint 134 code tag