bcgov / bcgov/range-web

Annual or twice per year required

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

Description

Annual or twice per year required ‘check-in’ – e.g., a little tick box that clients have to check by a certain date to confirm prior to the grazing season that they will be following the schedule as outlined in MyRA (or amend it if necessary) and after the grazing season that they followed the schedule (or otherwise will contact the Range Agrologist to follow up why not or what went differently). That would also eliminate the issue that clients have to reset their password because they didn’t log in for two years or keep forgetting their sign in credentials because they didn’t use them for too long. This is a neat idea. I have some additional thoughts but we could capture this notion for now.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified. Start by locating the MyRA schedule and client sign-in flows, then clarify the check-in timing, confirmation or amendment behavior, and Range Agrologist follow-up path with maintainers. The issue does not yet define completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.