-
Notifications
You must be signed in to change notification settings - Fork 109
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
Include link to plan in Request feedback email #1431
Labels
Comments
stephaniesimms
added
effort-small
less than 1/2 day of dev time
and removed
effort-small
less than 1/2 day of dev time
labels
May 1, 2018
confirmed w/ @briri that this is technically possible and straightforward. placing in backlog. |
stephaniesimms
changed the title
Review request email does not contain link to plan
Include link to plan in Review request email
May 21, 2018
stephaniesimms
changed the title
Include link to plan in Review request email
Include link to plan in Request feedback email
May 21, 2018
Bodacious
added a commit
that referenced
this issue
Jul 4, 2018
Looks good, thanks @Bodacious Have included a screengrab of the email here @stephaniesimms so you can double check quickly too. |
tested and all looks good. |
briri
pushed a commit
to CDLUC3/dmptool
that referenced
this issue
Jul 17, 2018
Reopening for verification after git cherry-pick |
links are present and working as expected. closing again. |
briri
pushed a commit
to CDLUC3/dmptool
that referenced
this issue
Jul 19, 2018
briri
pushed a commit
to CDLUC3/dmptool
that referenced
this issue
Nov 22, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour:
When an Org Admin receives an email requesting feedback on a DMP it would be really helpful if that automated email could include a direct link to the plan in question.
Actual behaviour:
Org Admin has to go through all plans where reviews have been requested on the plan menu
Steps to reproduce:
Request a review as an Org Admin
The text was updated successfully, but these errors were encountered: