Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

While working on this issue, we recognize all the events that Synapse sends message to our users:


EventNeed user action?Can turn off?Sent fromInclude user message?
1Someone invited me to a teamYes
Synapse NotificationYes
2Someone accepted my invitationNo
Synapse NotificationNo
3Someone requested to join my teamYes
Synapse NotificationYes
4Someone granted my requestNo
Synapse NotificationNo
5Someone submitted a submission for my teamNo
Synapse NotificationNo
6Someone requested to view my entityYes
SWCYes
7Someone shared an entity with meNo
SWCNo
8Someone sent me a messageNo
Any client & emailYes
9I created a verification submission

Synapse NotificationNo
10My verification submission status has changedNo
Synapse NotificationYes
11A new thread has been createdNoYesBroadcast Message WorkerNo
12A new reply has been createdNoYesBroadcast Message WorkerNo


From this list, 6 and 7 should be sent from Synapse Notification instead of sending from SWC. In fact, in 

Jira Legacy
serverJIRA (sagebionetworks.jira.com)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdba6fb084-9827-3160-8067-8ac7470f78b2
keyPLFM-4079
 user asked that we have the same behavior when the ACL is changed from different clients.

...