...
From this list, 6 and 7 should be sent from Synapse Notification instead of sending from SWC. In fact, in
| Jira Legacy |
|---|
| server | JIRA (sagebionetworks.jira.com) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | ba6fb084-9827-3160-8067-8ac7470f78b2 |
|---|
| key | PLFM-2578 |
|---|
|
user asked that we have the same behavior when the ACL is changed from different clients.
Also, | Jira Legacy |
|---|
| server | JIRA (sagebionetworks.jira.com) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | ba6fb084-9827-3160-8067-8ac7470f78b2 |
|---|
| key | SWC-3545 |
|---|
|
could be solved by adding an API for requesting access. Email should be send from the backend as a Synapse Notification email.Users requested that after the immediate fix, we would also provide the following:
...
