|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Mayo/Jason||We have run into multiple issues where the performance on the DEV tier has be a problem due to Mayo not being able to replicate the slow points due to the drastic difference in DEV resources. We discuss this with the systems team and they requested us to put in a DRT ticket that provides the specs to match the Mayo DEV server.||08/30/13||7/16/2014||A new development server has been procured and is currently being setup. This AI will be closed.|
|Area of Interest||Details|
Reviewing the tasks for the Lucene update.
|Report Writer||On hold until we complete the 2.6 Term Browser deployment.|
Provided a new tag for the 2.6 release to QA. Still having an issue with the AppScan. The container is running out of memory on what appears to be something with the value sets functionality. We are having an issues getting what exactly AppScan is trying do when the application errors out. We have made several attempts to fix through code changes and configuration updates based on what we are seeing in the application logs.
|Meta Download Validation App|
|Term Suggestion Form|
Term Suggestion Form 24 release is now live on production.
Resolved a commons-lang jar backward compatibility issue -- commons-lang3-3.1.jar is not compatible with commons-lang-2.4.jar.
|NCITERM-649||Value Sets - Release File View: Can't perform any Simple Searches when in the Release File View.|
Fixed in Tag 2015-02-25.2-v2.6
|NCITERM-650||Super script tag shows up on the Term Type popup page.||Fixed|
|NCITERM-651||Value Sets page caching contains search.|
Unable to reproduce.
|NCITERM-652||When selecting a Concept from any Hierarchy Tree, once the concept come up, clicking on View In Hierarchy does not render the Hierarchy Tree||Fixed|
|NCITERM-653||Value Sets: When hovering over the Selected Value Sets link, the popup list does not show up.||Fixed|
|Area of Interest||Details|
|Term Browser 2.6 Release||Continue review fixes and deployment.|
|NCIm Browser 2.5 Release|
Deployment to the DEV tier.
|Report Writer||Develop Project plan for 2.1 release.|
|Term Browser 2.5 Release||Deployment to the Stage tier.|
|Term Form 2.4 Release||Deployment to the DEV tier.|
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>|