Jan 27 - Feb 10, 2014
Executive Summary
Overall Status
Sprint status is excellent. The Product team initially pointed and prioritized the following themes and tasks for Sprint 124 comprising 48 points. The team completed 44 points for this sprint. The team completed all the tickets related to the primary theme for this sprint which was Security Scan Analysis and Resolution.The 4 points that were not completed were additional tickets pulled into the sprint for which the coding was complete but regression tests/QA was not completed.
Burndown
Sprint Themes and related tickets for Sprint 124:
- Partner and Community support
- Continued work with the NIST team(CONN-768)
- A new CONNECT system was set up for NIST testing to separate it from the machine used for DIL testing, thereby providing the team with greater flexibility as we continue to support both efforts.(CONN-799)
- Had a follow-up discussion with NIST. Pending issues see CONN-805
- NIST to fix Reply-To so that it will be sent.http://exchange-specifications.wikispaces.com/share/view/65871558
- Attribute statement nesting. Open question with spec factory. CONNECT has not made any changes yet, we do have a backlog to allow for a single nested attribute statement. At this point it seems that NIST would need to fix to accept both flavors - single attribute statement with all attributes nested as well as support each attribute within its own attribute statement. http://exchange-specifications.wikispaces.com/share/view/65871558
- hl7:CE vs CE for xsi:type http://exchange-specifications.wikispaces.com/share/view/66017850
- Community Implementation support
- Release 4.2.1 rebranding.(CONN-798, CONN-783, CONN-772)
- Sprint 116 rebranded to be Sprint 4.2.1.
- See wiki page for details and binaries - https://developer.connectopensource.org/x/YABWCg
- eHealth Exchange Participant test cases were executed successfully
- Release 4.2.1 rebranding.(CONN-798, CONN-783, CONN-772)
- Confluence update/upgrade (CONN-706)
- Prepared for migrating COnfluence to Atlassian On Demand. .
- Updated plugins and pages to remove the unsupported markups and macros/plugins.
- Attachments moved to ftp site to facilitate migration
- Continued work with the NIST team(CONN-768)
- Security scan analysis and resolution(CONN-669,CONN-760 user story and supporting tasks)
- This was the primary focus in Sprint 124. The team addressed all the Critical and HIgh findings from Fortify.
- Some of the issues identified by the Fortify scan were fixed in code and some were addressed with documentation. See wiki page with details - Fortify Install notes
- HIEM was removed from the codebase (CONN-771)
- HIEM was not refactored in 4.X and also included many security vulnerabilities in code that were discovered as part of Fortify. Since there is no partner in the Exchange using HIEM this service has been removed.
- Testing Improvements
- <jvm-options>-Dorg.connectopensource.enablejmx=true</jvm-options> has been permanently added to domain.xml template(CONN-775)
- Infrastructure improvements
- Ability to tag and generate binaries from any branch specified (CONN-786) which helps simplify the release process for binaries generation.
- Infrastructure migration for Terremark (CONN-778)
- GFE cleanup of configurations and servers
- Inventory management and documentation
- Direct functional enhancements
- Verify Direct requirements and current approach. Notes from the discussion can be found at - https://developer.connectopensource.org/x/BQB2Cg
- Bugs that were fixed
- Extract slots always gets one last value from the slots list (Adapter) (CONN-484)
- SAML Assertion AuthzDecisionStatement resource is passed from the adapters to the external parties 'as is', failing the DIL test MA-1092_AuthzDecisionStatement_Resource(CONN-612)
- Resource will always be updated to include the URI.
- SAML Attribute PurposeOfUse missing namespace for the @type attribute(CONN-740)
- Ongoing Custodial Agent Duties
- CONNECT 4 Blogs and Forum posts
JIRA Planning Board of Committed User Stories for Sprint 125
* Issue added to sprint after start time
Completed Issues | |||||
|---|---|---|---|---|---|
| Key | Summary | Issue Type | Priority | Status | Story Points (35) |
| CONN-691 | Default SAML Issuer value being used in all SOAP Header Security sections even though a valid X509SubjectName is defined in the private SSL certificate |  Bug |  Minor | CLOSED | 3 |
| CONN-759 | As an adopter interested in interoperabilty and health data exchange, I want to see a CONNECT demo so that I understand how CONNECT is used to exchange health data and how it interacts with other supporting MPI and repository systems |  User Story | Minor | CLOSED | 0 |
| CONN-800 | Resolve known "statefulness" in unit tests | Bug | Minor | CLOSED | 1 |
| CONN-804 | Validate the new NIST Test environment in GFE (GFE-ONC-WDEV12.connect.org -192.168.34.3) |  Task | Minor | CLOSED | 2 |
| CONN-808 | As a CONNECT developer, I want integration tests moved out of the build (and replaced with JUnit tests when necessary) so that tests are scoped appropriately. | User Story | Minor | CLOSED | 0 |
| CONN-810 | Regression suite tests for Greenmail | Task | Minor | CLOSED | 2 |
| CONN-811 | Add JUnit tests for mail classes for Direct/ Address Parsing package | Task | Minor | CLOSED | 3 |
| CONN-813 | Support for GFE/TERREMARK infrastructure activities for CONNECT | Task | Minor | CLOSED | 3 |
| CONN-816 | As a CONNECT adopter, I want new features and bug fixes are re-tested so that new functionality is validated prior to release | User Story | Minor | CLOSED | 5 |
| CONN-820 | Add JUnit tests for mail classes for XDR package | Task | Minor | CLOSED | 3 |
| CONN-821 | Add JUnit tests for mail classes for Mail package | Task | Minor | CLOSED | 3 |
| CONN-823 | As a CONNECT developer, I want to set up an environment for a HIMSS 2014 demo. | Technical Story | Minor | CLOSED | 2 |
| CONN-824 | As a CONNECT developer I want to rebrand the portal with CONNECT theme to demo at HIMSS 2014 | Technical Story | Minor | CLOSED | 1 |
| CONN-825 | As a CONNECT developer I want to do a dry run of the HIMSS 2014 demo with good data. | Technical Story | Minor | CLOSED | 2 |
| CONN-826 | Setup Interop test environment on Linux with JBoss/CONNECT 4.2.1 | Task | Minor | CLOSED | 3 |
| CONN-852 * | Review of Bug Fixes Made to Aurion | Task | Minor | CLOSED | - |
| CONN-853 * | Unit tests for Remaining DirectCore Classes for Target Coverage | Task | Minor | CLOSED | 2 |
| CONN-854 * | QA Task for DirectCore Unit tests | Task | Minor | CLOSED | 0 |
| CONN-857 * | Research VA deploy issue in WLS 12c Windows | Task | Minor | CLOSED | - |
Issues Not Completed | |||||
| Key | Summary | Issue Type | Priority | Status | Story Points (2) |
| CONN-815 | As a CONNECT adopter, I want a Release test plan for 4.3 so that the community understands how 4.3 has been tested prior to making it available | User Story | Minor | IN PROGRESS | 2 |
Issues Removed From Sprint | |||||
| Key | Summary | Issue Type | Priority | Status | Story Points (0) |
| CONN-779 | As a CONNECT adopter, I want 4.3 to be install tested so that the installation is successfully validated in the supported environments | User Story | Minor | OPEN | |