Open zoeyli-46 opened 2 months ago
Potential to be broken down into multiple user stories
We'll need to figure out how to do the snapshot thing in the db
Update AC based on pending decisions from business area
Splitting into multiple stories by @zoeyli-46
Deletion Candidate Reason:
Registration purpose and operation info steps have been combined into a single step
PR: https://github.com/bcgov/cas-registration/pull/1990 Ticket: https://github.com/orgs/bcgov/projects/122/views/2?filterQuery=&pane=issue&itemId=69561695
Deletion Candidate Reason:
Registration purpose and operation info steps have been combined into a single step
PR: #1990 Ticket: https://github.com/orgs/bcgov/projects/122/views/2?filterQuery=&pane=issue&itemId=69561695
I think we still need this one. I was trying not to wildly expand the scope of the one I'm working on, so I'm only adding the 'select operation' part, not the add part.
@zoeyli-46 and @shon-button I've updated this ticket
Dependencies
Description:
As an industry user, given that the operation has been added to my operator, I can register the operation.
Figma
Acceptance Criteria:
Given I am on the first page of the registration form When I click on the Operation dropdown, Then the list of operations will only show operations that have been added but not yet registered (this dropdown was implemented in #1899 but it's not yet filtered on registration status)
Given that I selected an operation from the dropdown, Then the operation form of the selected operation will appear, so that I can review the information and be able to edit it
Given that I am on the operation information page of the New Registration form, When I click on the Add a New Operation button Then I can see an empty operation form in edit mode, so that I can fill it out
~Given that I selected EIO as my registration purpose Then I see fewer fields on the operation information form. I only see~
Development Checklist:
Changes to make to Operation data model:
Changes to make to document_type data model:
Changes to make to bc_obps_regulated_operation data model:
Create new enum class Registration Category:
Changes to make to
operation_ownership_timeline
data model (repurposing this - it turns out we don't need to track ownership of an operation, but we do need to track who the "designated operator" of an operation is, which can change):operation_operator_timeline
(or if you can think of a better name, use that instead!)Changes to make to
facility_ownership_timeline
data model (repurposing this - as with operations, we don't need to track facility ownership, but rather just what operation the facility belongs to, which can change over time):[ ] rename table to
facility_operation_timeline
(or if you can think of a better name, use that instead!)[ ] update comments on model to reflect that the data captures the relationship between the facility and operation it falls under, not facility ownership
[ ] fields in table are unchanged
[ ] Meets the DOD
Definition of Ready (Note: If any of these points are not applicable, mark N/A)
·Definition of Done (Note: If any of these points are not applicable, mark N/A)
Notes: