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

Its not easy to identify new updates in a case #15

Open
timapril opened this issue May 3, 2021 · 0 comments
Open

Its not easy to identify new updates in a case #15

timapril opened this issue May 3, 2021 · 0 comments
Labels
enhancement New feature or request p3_low Priority: low

Comments

@timapril
Copy link

timapril commented May 3, 2021

When I receive emails from VINCE about an update to a Case I am involved with. I end up needing to review the entire case very carefully to determine what chances are visible to me. There are a few ways I can think to address this, while still avoiding sensitive information the email message.

  1. A change log in the case view which has links to the updated entities and the timestamps of each change.
  2. Links from the email could highlight specific posts or sections of the UI to draw the user to the updated Information.
  3. Have the option of users to mark data items as read or not. Things that have not been "read" should probably be displayed differently. A change to an item should reset its read status.
@zmanion zmanion added enhancement New feature or request p3_low Priority: low labels May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request p3_low Priority: low
Projects
None yet
Development

No branches or pull requests

2 participants