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.

Sign up for GitHub

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

Jump to bottom

Implement notifications for publication workflow #5

Closed
4 of 6 tasks
mark-dce opened this issue May 18, 2017 · 1 comment
Closed
4 of 6 tasks

Implement notifications for publication workflow #5

mark-dce opened this issue May 18, 2017 · 1 comment
Assignees
@bess @no-reply

Comments

@mark-dce
Copy link
Contributor

mark-dce commented May 18, 2017 •
edited by bess
Loading

STORY
As a archives manager, I would like my staff to get meaningful notifications, so that they know when new items have changed status.

DETAILS
This is closely related to #3 which implements the workflow and just created placeholders for the various notifications

ACCEPTANCE

  • notification for new submissions
  • notification for review complete
  • notification for publication
  • notification for changes requested
  • notification for unpublish
  • other notifications as identified in Implement publication workflow #3
@mark-dce mark-dce mentioned this issue May 18, 2017
Closed
4 tasks
@no-reply no-reply mentioned this issue Sep 5, 2017
Merged
@bess bess self-assigned this Sep 11, 2017
@bess
Copy link
Contributor

bess commented Sep 17, 2017

We removed the "review" part of the workflow, and the "changes requested", so no notifications for those.

@bess bess mentioned this issue Sep 17, 2017
Closed
@no-reply no-reply mentioned this issue Sep 19, 2017
Merged
@no-reply no-reply self-assigned this Sep 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bess bess

@no-reply no-reply

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bess @no-reply @mark-dce