|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Area of Interest||Details|
The systems team shutdown the 6.0, 6.1 and 6.2 containers with all the URL's now pointing to the 6.3 container.
Leaving the 5.1 production and stage container up. Stage will be shutdown when the latest data is deployed.
Need a decision on where this functionality is going to go to start creating trackers and scope document.
QA team completed deployment to QA, has run the automated test which all passed, and now putting in a ticket for the appscan and is starting to review the new feature items.
|Meta Download Validation App|
|Term Suggestion Form|
SSL has been applied to the Term Suggestion application on QA. Seems to be working correctly.
|NCIm Browser||The EVS requirements group decided to proceed with 2.6 release of the NCIm Browser. The 2.6 release would include automated testing, LexEVS 6.3, AppScan fixes, Search fixes that came up from Term Browser development.|
|LEXEVS-1132||JSONObjects contains in the JSON String returned by Tree Extension API are not sorted properly.|
Modified code to counter potential Cross-Site Scripting (XSS) attacks.
Resubmitted an appscan request subsequently.
Rerun of the appscan yields no high or medium vulnerability.
|NCITERM-691||View In Hierarchy tree node expand/collapse issue.||Performed trouble-shooting on the reported issue. The root cause might be related to that the JSON string returned by the Tree Extension API is not always sorted by node labels.|
Generated URL is not version specific.
|Area of Interest||Details|
|Term Browser 2.7 Release||Test and deployment of the 2.7 release.|
|NCIm Browser 2.6 Release||Planning for development of 2.6 release.|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|04/10/14||Deployments have been taking long periods of time. There is a lot of overhead getting through the iters||H||H||Speaking with members of the QA team to find ways to streamline the testing/deployment process||Finding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels.|
|7/17/2014||Deployment of software, even small upgrades, have been a lengthy process.||This especially affects smaller releases in which there are security or bug fixes.||The Agile practices migration have been put on hold for now.|
|09/10/2014||Getting the environment in place for the Mayo trip to NCI.||Need to get each of the environment (DEV,QA,Stage) in place before the Mayo trip on September 22nd. We are currently one week behind. The impact is that the Mayo developer will be onsite to work on the deployments and the tiers will not be in place.||Currently we only have the DEV environment setup for the LexEVS API>|