Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replacement workflow in the case of a change of tenure holder #1052

Open
3 tasks
micheal-w-wells opened this issue Nov 24, 2023 · 0 comments
Open
3 tasks

Replacement workflow in the case of a change of tenure holder #1052

micheal-w-wells opened this issue Nov 24, 2023 · 0 comments
Assignees
Labels
Task Work that cannot be written as a User Story

Comments

@micheal-w-wells
Copy link
Collaborator

  • when tenure holder added via FTA - plan is no longer legal regardless of dates on it - current working plan becomes a draft but keeps content, notification sent to all AH on this new plan
  • the last approved plan shows up in versions, but only for agreement holders that were on it (might not be the new one)
  • email anyone on the new plan that we have an email for that everyone needs to get a bceid so they can act on their plan and view it in myra
@micheal-w-wells micheal-w-wells added the Task Work that cannot be written as a User Story label Nov 24, 2023
@brijesh-amin brijesh-amin self-assigned this Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Work that cannot be written as a User Story
Projects
None yet
Development

No branches or pull requests

2 participants