Sprint 13

517 - Internal user: See unread messages in work queue

• unread messages are bolded on the work queue and considered read when the document link is clicked

1472 - Mobile Docket View

• making the docket view mobile friendly

531 - Practitioner: Filing an Entry of Appearance or Substitution of Counsel

• ability to associate a practitioner to a case

837 - Court: Time-Out due to Inactivity

• displaying a modal when the user has been inactive
• logs the user out after 1 hour of inactivity (no mouse movement or key strokes)

316 - Generation of cover sheet for all uploaded documents

• generates a cover sheet for all uploaded documents

Sprint 12

Merge pull request #1479 from flexion/code-review-fixes

Code review comments addressed

Sprint 11

Court User: Creating a case on behalf of paper-filing petitioner #311

• Start a new case for a paper-filed Petition
  

Epic 2 Clean-Up #367

• Various tasks to correct

• Add Case Caption to Petition Document Detail
  

• Send Message form / Create New Message
  

Parties: Assign Doc Type for External Filing #269

• Parties are able to select a document type from a list of Court-approved documents.

• Add File Document Button for petitioners, practitioners, and respondent
  

• Desktop category selection
  

• Mobile view
  

Sprint 10

Sprint 10

Bugs: Found during Sprint 10 Review Prep #1140

• various bugs to fix

Petitions Clerk: Review Party Type, Contact Information, and other Metadata #699

• redesign to put into different tabs

Petitions Clerk: Orders to be Issued following QC process #698

• adding various check boxes to the QC document details edit page which allows the petitionsclerk to mark orders

Create an AWS diagram #785

• created an aws diagram and added it to the repo (this diagram was created by hand)

Bug: 401 errors not sending users back to login screen #966

• fixing a bug which occurred when the user's token was expired but the app wasn't redirecting the user back to cognito to log in

Court User: Start a message thread #962

• ability to create a new message ( work item) on a document

Petitioner: Statement of Taxpayer Identification Number #786

• requiring the STIN document when creating a petition

Document-level message thread in document detail #359

• added sub tabs on the messages tab on the document details which allows a user to view all the pending / completed work items

Court: Ability to correct a case caption #310

• Added an "edit" button next to the case caption which displays a edit modal.

Deploy Steps

• You will need to run the management/management/bin/setup-jobs.sh script for these changes to deploy because we separated the deploy steps into separate jobs. Please refer to step 11 in the SETUP.md file

Sprint 9

Stories:

#776 - Petitioner: Login (Bare Bones)

• The user is able to login with the email / password they registered for in cognito

#654 - Petitioner: Ownership Disclosure Statement (ODS)

• adds the ability for corporations, LLCs, or partnerships to upload a Ownership Disclosure Statement

#307 - Select party type and enter appropriate contact information

• ability for the petitioner to select the party type

#313 - Petitioner: Automatic creation of case caption

• create the case caption automatically when a case is created

#655 - Petitioner: International and Other Domestic Addresses and Phone Numbers

• ability for petitioners to select domestic vs international addresses

#315 - Petitioner: Clean up petition form

• various tasks to clean up the petition form

#588 - Petitioner: Yes/No logic with respect to IRS notice

• adding yes / no radio buttons on the petition form for if the user had an irs notice

#783 - Petitions Clerk: View of document from Docket Record

• redirecting the user to the document details page when clicking on a document in the docket record

#782 - Petitions Clerk: Document Information Tab

• display the document info tab for a petition

Deploy Notes:

We updated both our Bastion and Jenkins AMI to the latest versions:

bastion - ami-0565af6e282977273
jenkins - ami-0fb512c4bdcf4cb27

To do the same, you should be able to just follow the steps in the SETUP.md for running the deploy-infrastructure.sh script. It will destroy both EC2 instances and recreating them; therefore, you will need to setup Jenkins following the same steps as before.

Sprint 8

Stories:

307 Petitioner: Select party type and enter appropriate contact information

Added a lot to the start a case.

776 Petitioner: Login (Bare Bones)

Setup cognito login functionality.

313 Petitioner: Automatic creation of case caption

Generating the case caption.

789 Petitioner: Registration (Bare Bones)

Setup cognito registration.

645 Petitioner: Verify that I am Filing Petition for Myself

Added some help text to explain the criteria for filing for myself:

644 Petitioner: Warning of timeliness of electronic Petition

We added a interstitial page before you can start a case which gives extra information required before you can start a case.

Jenkins Setup

• You'll need to add another ENV variable to Jenkins.
  • navigate to the configure system page in Jenkins: /jenkins/configure
  • add the following in global env variables: COGNITO_SUFFIX // ustc-efcms
  • COGNITO_SUFFIX is used for the cognito URL created after a deploy
• You'll need to setup a secret text credential in Jenkins:
  • navigate to the global credentials section in Jenkins: /jenkins/credentials/store/system/domain/_/
  • click Add Credentials
  • select Secret Text
  • let ID be USTC_ADMIN_PASS
  • let Secret be some secure password
  • USTC_ADMIN_PASS is the password used for the cognito admin user

Deploy Steps

Follow additional Jenkins setup described above before doing these ^

1. delete the cloud formation stack for efcms-stg on us-east-1
2. delete the cloud formation stack for efcms-stg on us-west-1
3. run deploy

Sprint 7

Stories:

514 Petitions Clerk: Review/QC of Petition

• login as taxpayer and start a case, login as petitionsclerk and find the case in the Section queue, click on the petition link:

676 Server Error Handling - Global Solution and Implementation

• go to any bad url like /iamabadurl

• try and login with "baduserbad!"

515 Petitions Clerk: Send Petition to Holding Queue for Service on IRS

• follow steps as in 514 then click the "Serve to IRS" button

516 Petitions Clerk/Supervisor: View/Edit cases in IRS Holding Queue (partial)

• on the same petition as in 515 note that it is in the section "sent" box, click on it to go to the document detail then click the "recall" button - note that petition/case moves back to the inbox on the section queue.

Notes

• The staging database should be cleared to support data changes in the schema before deploying.
• npm audit is issuing a warning for serverless-dynamodb-local. Because upgrading to version 1.0.2 is a breaking change it was agreed to temporarily disable the npm audit on the efcms-service project and
  provide a fix in Sprint 8.

### 514 Petitions Clerk: Review/QC of Petition 
* login as taxpayer and start a case, login as petitionsclerk and find the case in the Section queue, click on the petition link:

![screen shot 2019-02-08 at 8 27 28 am](https://user-images.githubusercontent.com/2058839/52484211-67906980-2b7b-11e9-9d31-61663fe73518.png)

### 676 Server Error Handling - Global Solution and Implementation
* go to any bad url like /iamabadurl 

![screen shot 2019-02-08 at 8 29 30 am](https://user-images.githubusercontent.com/2058839/52484340-b1794f80-2b7b-11e9-86f8-23ed0b792db6.png)

* try and login with "baduserbad!"

![screen shot 2019-02-08 at 8 30 31 am](https://user-images.githubusercontent.com/2058839/52484398-d40b6880-2b7b-11e9-9abd-1c16c20baf43.png)


### 515 Petitions Clerk: Send Petition to Holding Queue for Service on IRS

* follow steps as in 514 then click the "Serve to IRS" button

![screen shot 2019-02-08 at 8 31 41 am](https://user-images.githubusercontent.com/2058839/52484464-01f0ad00-2b7c-11e9-9cb3-a3881c6bc9c1.png)

### 516 Petitions Clerk/Supervisor: View/Edit cases in IRS Holding Queue (partial)
* on the same petition as in 515 note that it is in the section "sent" box, click on it to go to the document detail then click the "recall" button - note that petition/case moves back to the inbox on the section queue. 

![screen shot 2019-02-08 at 8 33 15 am](https://user-images.githubusercontent.com/2058839/52484577-4714df00-2b7c-11e9-8517-ea9d42303430.png)


### Notes

* The staging database should be cleared to support data changes in the schema before deploying.
* npm audit is issuing a warning for serverless-dynamodb-local. Because upgrading to version 1.0.2 is a breaking change it was agreed to temporarily disable the npm audit on the efcms-service project and
provide a fix in Sprint 8.```

=== npm audit security report ===

# Run  npm install serverless-dynamodb-local@1.0.2  to resolve 1 vulnerability
SEMVER WARNING: Recommended action is a potentially breaking change
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Moderate      │ Prototype Pollution                                          │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ node.extend                                                  │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ serverless-dynamodb-local                                    │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ serverless-dynamodb-local > dynamodb-localhost > rmdir >     │
│               │ node.flow > node.extend                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://nodesecurity.io/advisories/781                       │
└───────────────┴──────────────────────────────────────────────────────────────┘


found 1 moderate severity vulnerability in 3548 scanned packages
 1 vulnerability requires semver-major dependency updates.

Sprint 6

User Stories

#513 - Petitions Clerk/Supervisor: Assign Petition to Petitions Clerk (2.7)

Adding the ability for petitionsclerk to forward work items between other petitionclerks in the same section.

#404 - Court: Suffix on Docket Number (2.6)

Adding a suffix to the docketNumber anywhere that docketNumber is displayed

#402 - Petitioner: Enter Case Metadata (2.5)

Redesign of the start a case page to allow the user to enter metadata

#401 - Petitioner: Upload IRS Notice (2.4)

Added the ability for the user to upload an IRS notice (this was later removed on the 402 task because we are assuming the petitioner will combine their files into a single pdf before upload)

Deploy Steps

• delete all items from the efcms-stg dynamodb table

Sprint 5

User Stories

#406 - Internal User: View Work Items within Case

On the case details page, there is a new table at the top which displays any work item associated with the case:

#407 - Docket Clerk: Forward/Assign work from Docket Section work queue to Individual work queue

On the section work queue, the docketclerk has the ability to assign the work item to other docketclerks that exist in the system:

#113 Docket Clerk: Forward Stipulated Decision

On the document detail page, there is an option for an internal user to forward the work item to a different user:

Deploy Steps

• delete all items from the efcms-stg dynamodb table

Sprint 4

User Stories

#110 - Send Petition Package to IRS

• added a "submit to irs" button on the case details page for the "petitionsclerk" role login which allows them to mark the package as sent to the irs (not real sending functionality for this story at this point

#111 - Respondent - File and Answer

• added a File Document button on the case details page for the "respondent" role which navigates the user to another page which allows them to select a document type and upload

#112 - Respondent - File a Stipulated Decision

• similar to 111, but with a different file type (see image above)

#113 - Docket Clerk - Forward Stipulated Decision (In Progress)

Reminder, there are 4 logins now

• respondent
• docketclerk
• taxpayer
• petitionsclerk

Deploy Steps

• Login to Jenkins
• click on the ef-cms-shared job
• click on configure job
• change "script path" to "shared/Jenkinsfile"

Code Architecture Related Changes

• renamed business folder to shared
• no longer having separate tables for each entity type in dynamodb; instead, we are writing everything to a 'efcms-dev' table. This was an attempt to move away from a "relational" approach; the dynamodb best practices documentation suggests only having a single table for your application.
• removed the efcms-cases table
• removed the efcms-documents table
• removing the test cases that cover our lambda files since they are redundant tests; the same use cases are verified in the "shared" test cases