Non-Pilot Ministry - Fee Estimate Form Sync

[m-prodan]

• As a user
• I want the fee estimate/invoice I enter in AXIS, to be reflected in the new application for non-pilot Ministries
• so that I do not have to duplicate work by entering the same data

Assumptions & Scope This reflects the need for users handling non-pilot Ministries to have their fee estimates ready for deployment after they initially add and sync their request to the application. When a user goes to the fee estimate form, provided they have filled out the invoice/fee estimate on AXIS prior to them adding/syncing, the same information should appear and be visible.

The mapping from AXIS to our app can be found at the following link: https://bcgov.sharepoint.com/:x:/t/03521/EX1CTABBXY5Dg6lIYe5T8N4B5UY5Kb-mp1hD3KSls1ujfQ?e=yka9aa

Please note - there are two different fields for number of pages, which map to the same field in our app - see notes for more context.

What is IN scope?

What is NOT in scope?

Acceptance Criteria

Scenario 1: CFR Form Status - Original Value

• GIVEN I am on a fee estimate form for a non-pilot Ministry for the first time
• WHEN the page loads
• THEN the status will be automatically set to "In Review"

Scenario 2: AXIS Sync

• GIVEN I am on the fee estimate form for a non-pilot Ministry Team
• WHEN there have been any changes made to the file in AXIS
• AND those changes are mapped to the fees form
• THEN the AXIS Sync Banner will appear
• AND The AXIS Sync button at the bottom will become active

Scenario 3: AXIS Sync - Activation

• GIVEN I am on the fee estimate form for a non-pilot Ministry Team, and the AXIS Sync banner is active
• WHEN I click on the Sync to AXIS button
• THEN the AXIS Sync modal will appear
• AND there will be a button to save changes and cancel
• AND The AXIS sync modal will function consistent with the application's sync feature

...

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)

Validation Rules? (If yes, list here)

Design @xxx - please link the Design here

Definition of Ready

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

Definition of Done

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

[m-prodan]

Fees form for Non-Pilot Ministry - I've included a mapping of the invoice from AXIS to the values in our app.

cc: @lmullane @KaraBeach @JHarrietha-AOT

[m-prodan]

Updated story based on our discussion today.

[lmullane]

@abin-aot, @m-prodan, @arielleandrews, should this sync also happen from the request view?

[arielleandrews]

Decisions at refinement on Aug 16:

• Do analysis of the AXIS sync of invoice information prior to any work on this user story. The estimate of 13 includes some analysis work - will need to be re-estimated before coming in to the product backlog
• Separate sync function for CFR fee/invoice information than the sync on the request details page
• Separate banner information that will be specific to the fee/invoice information
• Request details will not be editable after AXIS sync