bcgov / bcgov/entity

As a staff member, I can correct a correction

Open
#6,562 1 comment 0 reactions 0 assignees View on GitHub
ENTITY - DO NOT USE STORY
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

## Story
As a staff user
I want to correct a correction
So that I can make more corrections to the **most current version** of a filing
_i.e. I should not be able to correct an old (pre-corrected) version of a filing, because that version is no longer valid_

## Background
This came up because of ops ticket #6445, LEYLINE ALTRUISM BC1275548. We corrected some parts, but not all, so the correction filing was incomplete and incorrect. We need to correct the correction. Can we, and should we? This ticket is to . . . .

## Acceptance Criteria
#### 1 - Correct a correction
GIVEN I am a staff member
AND I have filed a correction to a filing for an entity
WHEN I click the drop down next to a correction filing
THEN I can see the option to correct the filing
AND I can successfully complete the correction

#### 2 - Can't correct the original
GIVEN I am a staff member
AND I have filed a correction to a filing for an entity
WHEN I click the dropdown next to the **original filing that has since been corrected**
THEN I can see that the option to correct the filing is disabled
AND I cannot complete a correction to the original filing (that has since been corrected

## Definition of Ready

- [ ] Are the Acceptance Criteria defined?
- [ ] Does the user story speak to the value being created, and is understood by the team?
- [ ] Are the dependencies known/ understood? (to the our best knowledge)
- [ ] Is this user story small enough to be completed in one Sprint?
- [ ] Dev team accepts UI artifacts? (visual UX designs ready to go)
- [ ] Is it clear whether this work is intended for deploy or limited/staged-release?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.