bcgov / bcgov/range-web

Signature dialog improvements

Open
#1,166 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
9
Forks
11
PR merge metrics
No merged PRs in 30d

Description

When someone is the Agent of other people, they get a message after submitting that says that the other agreement holders are will be notified and asked for signatures even though it goes directly to final decision (if that’s what they chose), so that’s a bit confusing.
____________________________________________
Point 2 - might need more information, but I think that I understand. If there are two agreement holders and and agent for both, it should just say that they approved (or whatever) if there are three agreement holders and only two have an agent, then it should know that, but still say that the other agreement holder will be notified. This might be difficult but I will talk to Brij.
____________________________________________
Brij, I am not sure that I can change the email message where it is saying that it will be asking for the other signatures?


Here are the three that I can change.
____________________________________________
We have a generic email that goes out whenever plan status changes. MyRange does not send email asking for signatures. It is just the message that appears on the dialog box.

I can add an additional email template and modify code to send emails asking for signature or we can modify the message on the dialog box.

____________________________________________

We can change the dialog box to be clearer. Let me look at what Taylor wrote and see what will work for us.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names only the dialog shown after submitting an agreement and the generic plan-status email; no file, test, or entry point is provided. Start by locating that submission dialog and tracing how agent and agreement-holder status determines its message, then clarify the expected wording and verify the relevant submission scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.