bcgov / bcgov/range-web

INFO - Mandatory Amendment

Open
#707 3 comments 0 reactions 1 assignee Claimed by @LisaMoore1 View on GitHub
Dominant language
TypeScript
Stars
9
Forks
11
PR merge metrics
No merged PRs in 30d

Description

These are for thought — I’m open to discussion but each touches on an important principle that needs to be addressed (all content of #703 applies):
**AH initiated**
- [ ] draft amendment is not visible to staff until AH submits for either feedback or decision
- [x] all workflows beyond initiation follow same workflow as for original RUP (but it should be clear it is an amendment in progress)
- [ ] headers need to reflect amendment language
- ??Does that mean they should all be made more generic or review all and make more specific for amendments?
- [ ] AH can discard an amendment they initiated only BEFORE they submit

**Staff initiated**
- [ ] mandatory is the only type of amendment a staff person can initiate
- [ ] requires a button for staff to initiate a new version (amendment)
- other situation a staff person may need to create a new version are: (a) at time of RUP expiry or (b) when all (or a portion of information) is copied to a different RAN (usage and schedules can only be copied if both RANs have same usage info)
- (b) is a separate fairly infrequent scenario for down the road...maybe
- [x] staff may choose not to change any content but their message to the AH may indicate what the required changes are
- [x] all workflows beyond initiation follow same workflow as for original RUP (but it should be clear it is an amendment in progress)
- [ ] submit for feedback and submit for decision workflows/options apply
- [ ] headers need to reflect amendment language
- ??Does that mean they should all be made more generic or review all and make more specific for amendments?
- [ ] Staff can discard an amendment they start any time BEFORE they send to AH

**General**
- [ ] future DM workflow will apply (including right to impose conditions on approval) between options
- [ ] all mandatory amendments are in-progress until an approval decision is made

**Question**
- [ ] if an amendment gets submitted and signature process started but then a decision is made to recall/discard it how does that work?
- mutual decision?
- worth considering as it will sit there blocking future amendments

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.