Skip to content

Annual or twice per year required #1286

Description

@brijesh-amin

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    User StoryFeature written from a Users perspective focused on value

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions