KG - Notification Sharing Feature #2323
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://www.pivotaltracker.com/story/show/170109025
Background
Currently notifications sent to specific users are only visible to the person receiving or sending the message. For units with multiple providers this poses a problem as it is unclear what has been communicated. We propose that Overlords and Super Users be able to view the entire message history within a protocol.
Acceptance Criteria
1).When sending a notification related to a request, users should be able to publish/share a notification. Default to "share" when not selected otherwise.
2). On Messages page, add a third tab "View All Shared", which display shared notifications (history) on sub_service_requests that the logged in user has access to. This should be view-only for previous records, and shouldn't have the mark as unread/read functions.
3). In SPARCReport, add a new canned report to export all notification, with date and organization filters. The report should include: SRID, Request Organization, From, To, Date, Subject, Content.