Task Setup EnterpriseDB for HA & Recovery

Detailed Description

• [] install EnterpriseDB images to catalog
• [] deploy EDB to Prod namespace
• [] create backups
• [] sftp backups to Oracle server ?
• [] test recovery
• [] test removing of pods for HA

Sprint Goal

Acceptance Criteria

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• Acceptance Criteria Defined 1️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Task Label 1️⃣
• Assignee 2️⃣
• Sprint Goal (in line with the goal of the sprint) 2️⃣

Task names search API should be only accessible to those with the names_viewer, examiner or manager roles

Detailed Description

Add in the condition to the JWT role that requires a valid namex_ group user role

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Currently, a call to COLIN/NRO is made. This call should confirm that the corp_num is active and that the previous NR is rejected. Error messages are missing for the following states:
NR/Corp_num is present and in the valid state
NR/Corp_num is not in valid format
NR/Corp_num is in valid format, but invalid state

Sprint Goal

Acceptance Criteria

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• Acceptance Criteria Defined 1️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Task Label 1️⃣
• Assignee 2️⃣
• Sprint Goal (in line with the goal of the sprint) 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a partner I would like an updated approval guidebook/manual to help clients make decisions and to be able to explain decisions made.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a partner (lay form) I want the descriptive and distinctive word st be published so that I can help my clients better name choices for submission.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

@forgeuxGH5 commented on Mon Nov 19 2018

Examiners want to see the NR's they've worked on in the past day (and probably over longer periods) in part to help them track their performance.

Add a dropdown filter to the Last Modified column similar to the filter for the Submitted Date.
Values in the dropdown:
Today
Yesterday
2 days
7 days
30 days
All

This filter, combined with a username filter will allow Examiners to see the list of NRs they have worked on over the selected period.

Definition of Done:
Examiners can see the list of NRs they have worked on over a selected period (at least the past day).

Name decision - display the list of conflicts when there is no decision text for older NRs

Description:

Many older (pre-namex) NRs do not have decision text, but will have a list of conflicts. If there is no decision text to show in name choice (CompName component) show list of conflicts instead if that data exists.

Depends on #1096 for meaningful data to exist.

Affected by design decision made for #1100 .

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

UX Changes

Description: Implementing the front end changes based on API research - Dependent on

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Need a way for to automatically determine that there are multiple words in the distinctive .

eg RED PLATINUM CONSULTING SERVICES LTD.

Sprint Goal

Acceptance Criteria

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• Acceptance Criteria Defined 1️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Task Label 1️⃣
• Assignee 2️⃣
• Sprint Goal (in line with the goal of the sprint) 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As an examiner I want to be able to upgrade a request to a priority request so that the client doesnt have to do it.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• BDD Pseudo-Code 2️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Scenario Label 1️⃣
• Assignee 1️⃣
• Linked Story 1️⃣

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Sprint Goal

Acceptance Criteria

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• Acceptance Criteria Defined 1️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Task Label 1️⃣
• Assignee 2️⃣
• Sprint Goal (in line with the goal of the sprint) 2️⃣

Story

As an examiner I want to be able to display and edit the appropriate submission details so that I get the appropriate information for each submission.

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")

GIVEN the NR is the current one the examiner is working on and it has a status="IN PROGRESS"
WHEN the request_type is displayed
THEN show or hide the appropriate fields on the screen.

Acceptance Criteria

-same logic and behaviour as in NRO

Issue Checklist

• BDD Pseudo-Code
• Estimate
• Priority Label
• Story Label
• Assignee
• Linked EPIC

Definition of Done

• Analysis/Design
• DB
• UI
• Integration Points
• Logic
• Test Script

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As an examiner I want the wait time included in the client's notification so that we get less class asking us the wait time.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• BDD Pseudo-Code 2️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Scenario Label 1️⃣
• Assignee 1️⃣
• Linked Story 1️⃣

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Sprint Goal

Acceptance Criteria

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• Acceptance Criteria Defined 1️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Task Label 1️⃣
• Assignee 2️⃣
• Sprint Goal (in line with the goal of the sprint) 2️⃣

Replace_With_Short_Descriptive_Name

Description: Keycloak Role Assignments for 3 new roles

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Currently NRs are hard coded into pm collections that newman runs.
- this means that when db is refreshed and NRs change that tests will fail

Could have the NR nums put in as globals and test multiple

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a reuestor/submitter I want to be able to et my notification via text message so that I don't have to check my email.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• BDD Pseudo-Code 2️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Scenario Label 1️⃣
• Assignee 1️⃣
• Linked Story 1️⃣

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Sprint Goal

Acceptance Criteria

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• Acceptance Criteria Defined 1️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Task Label 1️⃣
• Assignee 2️⃣
• Sprint Goal (in line with the goal of the sprint) 2️⃣

Planning and Research

Description: Research UI redesign

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As an examiner I want the system to automatically rate/score the name request on the likelihood that it will be approved.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• BDD Pseudo-Code 2️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Scenario Label 1️⃣
• Assignee 1️⃣
• Linked Story 1️⃣

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Sprint Goal

Acceptance Criteria

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• Acceptance Criteria Defined 1️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Task Label 1️⃣
• Assignee 2️⃣
• Sprint Goal (in line with the goal of the sprint) 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a names examiner, I want to be able to do a Google search on a name from within the name examining screen, so that I can understand more about the business to make a decision.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a name examiner, I want the system to tell me the industry of the trademark match of the name request, so that I can decide if it's a valid conflict.

Inputs(Data)

Trademarks should include all Active trademark status in All active.
The "All active" category includes all marks with the following statuses: formalized; searched; default—searched; approved; advertised; proposed opposition; opposed; allowed; default—allowed; refused—appeal in progress; registered and protected, including section 9 marks of the Trade-marks Act for which a public notice has been given; plant variety denominations; geographical indications that have been entered on the list and for which protection has been sought and not yet entered on the list; and marks of the Royal Canadian Legion, the Canadian General Council of the Boy Scouts Association or the Canadian Council of the Girl Guides Association.

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Run nro-get-decision-data script in production

Description:

This task is to run the nro-get-decision-data script in production to populate decision text and conflicts in older (pre-Namex) NRs.

This is a run-once script that will be run in batches in a job. It does not go through an existing pipeline.

See related task bcgov/name-examination#1096 for SQL for steps below.

Steps to deploy:

• create view in Oracle
• create tracking table in Postgres and grant permissions
• populate tracking table in Postgres
• tag image with "prod" tag (in TOOLS project)

oc tag nro-get-decision-data-runtime:latest nro-get-decision-data-runtime:pprod

• schedule job in prod environment (in PROD project)

oc process -f cron-nro-get-decision-data.yml -p ENV_TAG=prod
oc process -f cron-nro-get-decision-data.yml -p ENV_TAG=prod | oc create -f -

Acceptance / DoD:

• Product Owner advised if task >= 1 full-day, or forms part of the business day
• Requires deployments
• Test coverage acceptable
• Peer Reviewed
• Production burn in completed

Oracle setup for TLS 1.2

Description:

The OpenShift HTTPS connections are required by OCIO to restrict connections to TLS 1.2. When this was previously implemented it broke our connections from Oracle to the solr and namex feeders. It was temporarily rolled back in OpenShift, but they will again put in the TLS 1.2 restriction in the near future.

Oracle 11 by default does not support TLS 1.2, but it was patched in non-prod on 2018-11-18 and will be patched in prod on 2018-11-25. This ticket is to cover the wrangling of the DBAs from Registries and DXC, and to perform as much testing as is possible.

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a names examiner, I want the system to provide suggested improvements for a rejected name request, so I don't have to provide these manually to help the client be successful on their second request.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Race condition can exist when user (customer or examiner) starts an edit in NRO, but before they complete/save the edit the NR is pulled over to Namex and marked as held (status H) in NRO data.

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a partner I want to be able to search the same things as an examiner so that I can help my clients get their name request approved.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Currently when an NR is edited in Namex, the request table previous_request_id column is being updated. The previous_request_id in the names db is only used by NRO for Re-applys (RESUBMIT) and must not be updated by Namex. This was mistakenly used to store Previous NRs associated with a request type such as assumed name but is actually store din additional info in NRO only.

Replace_With_Short_Descriptive_Name

Description: Due to TLS changes, pull toNameX instead of pushing from Oracle.

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Replace_With_Short_Descriptive_Name

Description: Implementing and handling:

• s
• 's
• s'
• double letters
• 'and'
• designations
• exact-match to ignore the star

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Task Choose and implement an asynchronous eventing system

Detailed Description

Sprint Goal

Acceptance Criteria

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• Acceptance Criteria Defined 1️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Task Label 1️⃣
• Assignee 2️⃣
• Sprint Goal (in line with the goal of the sprint) 2️⃣

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a partner(law firm) I don't want to worry about distinctive and descriptive words for the name request submission or the notification I get back as it doesn't mean anything to my client.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Scenario

BDD Pseudo-Code (GIVEN "context" ... AND "more context" ... WHEN "this action occurs" ... THEN ..."result")

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• BDD Pseudo-Code 2️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Scenario Label 1️⃣
• Assignee 1️⃣
• Linked Story 1️⃣

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

Sprint Goal

Acceptance Criteria

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• Acceptance Criteria Defined 1️⃣
• Estimate 2️⃣
• Priority Label 1️⃣
• Task Label 1️⃣
• Assignee 2️⃣
• Sprint Goal (in line with the goal of the sprint) 2️⃣

Research how COBRS does its searches

Description:

Extract algorithms from COBRs PL/1 that are used to do the searches against names

Acceptance / DoD:

• docs stored in GitHub

• run jest tests within namex-web pipeline
• send feedback to slack and jenkins interface

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a manager, I want to create an appeal letter that saves with the name request, so that...

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Replace_With_Short_Descriptive_Name

Description: Due to the TLS changem moving the feeder to NameX to pull the data instead of Oracle pushing the data.

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a citizen I would like a diagram of the name approval workflow so that I better understand the process and know what to expect.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

EDIT - API Changes

Description:

This is a parent task - broken down to sub-issues found in the dependencies list below.

Research and implementation of new roles and work flow for editing.
Breaking edit from examine while maintaining NRO Lock
Back to queue
what can be edited when (before/after closed) and by who (viewer/examiner/admin).

Per decisions made week of Nov 26:

Before       |    During     |     After     
examination  |  examination  |  (completed)
_______________________________________________________________________
     Y       |       Y       |      *1     | Request type
     Y       |       Y       |      Y      | Submission details (contact info, additional info, prev nr, corp num, nwpta, anything else)
     *2      |       *2      |      N      | Names 
     n/a     |       n/a     |      Y      | Expiry Date
     Y       |       Y       |      Y      | Comments

*1 - only within same entity type
*2 - with system-generated comment "from x to y"

Roles - editors and examiners can edit everything all the time, with exceptions noted below.

Questions for Scott take to examiners:

1. editing name after complete - only examiners?
2. do they want indication of NR having been edited?
3. expiry date edit - only examiners? A from Kaine: no, everyone

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a names examiner, I want the system to automatically process simple name requests so that I can spend my time on the complex, challenging requests.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Solr - Use Delta Imports

Description:

The current approach to keeping the cores in sync is error prone and overly complicated:

• Solr data imports are a direct call from Solr to the Oracle views.
• Solr updates are an Oracle package that sends the update to the solr-feeder OpenShift web service, which then sends the updates to Solr.

Solr has the ability to use the same Oracle view to determine changes in data. It requires a way of determining the freshness of the data in the view, such as a timestamp indicating the most recent change to the data.

The following tasks need to be completed:

1. Create a new REGISTRY.SOLR_CONFLICTS_CORE_VW view in Oracle that includes a timestamp. This view must respect future effective dates (#83).
2. Create a new NAMES.SOLR_CONFLICTS_CORE_VW view in Oracle that includes a timestamp. This view must respect future effective dates (#83).
3. Update the Solr dataimport configuration for the possible.conflicts core to use the SqlEntityProcess with the delta import queries.
4. Change the names core to only include the fields necessary for the front-end. Remove name_instance_id, choice_number, corp_num, request_id, request_type_cd, name_id, and start_event_id.
5. Create a new NAMES.SOLR_NAMES_CORE_VW view in Oracle that includes a timestamp. This view must respect future effective dates (#83).
6. Update the Solr dataimport configuration for the names core to use the SqlEntityProcess with the delta import queries.

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a consenting body, I want names examiners to be able to process simple consents themselves (by adding our criteria to theirs), so that the client doesn't need to contact me for consent.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As an examiner/submitter I want to be able to upload my consent form if I already have it so that the approval process is completed and I can register my company.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Update the developer and database docs

Description:

• Fixed a typo making copy/paste now possible in the database doc
• Added the new naming syntax for branches, where we now prefix with the issue_number

Acceptance / DoD:

• Peer Reviewed

Replace_With_Short_Descriptive_Name

Description:

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

Describe the bug
Solr needs to be synced daily, preference towards an automated solution (and more preference toward fixing the problems that are causing the sync issues).

Expected behavior
That the Solr cores "names" and "possible.conflicts" and Oracle databases (NamesP/CPRD) are in sync

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a names examiner, I want NRO to include basic validation on the distinctive and descriptive fields so that I don't receive as many names that are missing these.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a citizen I would like some examples of names that require consent on the website so that I can make informed decisions about my name.

Inputs(Data)

Outputs(Data)

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

Handle Special Characters

Description: Implementing and handling synonym bucket special characters, remove + sign

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

just a test to close right away

Task (Use for Work not Directly related to a Story but supports the Sprint Goals)

Detailed Description

When a name is consumed, you cannot allow a reset in NAMEX.

Acceptance Criteria

Story

Story Sentence (As a "user type" I want a "goal" so that "benefit".)

As a citizen I want better information on the NRO site so that I can perform a submission quickly and efficiently.

Inputs(Data)

Outputs(Data)

Video Guide in selecting a name.
Graphic on how terms are used.
Describe nature of business.
Improved Search disclaimer

User Research Test Results

Definition of Done (:one:-Mandatory to add to the Backlog, :two:-Mandatory to add to the Sprint Backlog)

• User Story 1️⃣
• Priority Label 1️⃣
• Story Label 1️⃣
• Linked EPIC 2️⃣
• Linked Scenarios 2️⃣
• Inputs(Data) 1️⃣
• Outputs(Data) 1️⃣
• Attached Sketch/Mock-up
• User Research Test Results

UI Research

Description: Research UI changes needed to support new edit workflow

Acceptance / DoD:

• Design / Solution accepted by Product Owner
• Test coverage acceptable
• Peer Reviewed
• UX Approved
• PR Accepted
• Production burn in completed

The office_vw used by the COLIN API returns rows that have a null delivery_address_id which the API tries to link with the ADDRESS_VW which causes an error on the front-end.
No null address ids should be available to the api.

Bug:
The fix went in but we did not update all occurrences of the call to the view in the colin api. The test only addressed the one call. My mistake. The user is no longer receiving a 500 error but is getting a fdw error. I think this is relatively low priority.