Closed orlando closed 5 years ago
Are we sure we need this for launch? 100% this will not be doable before October 1st at our current velocity.
This is important, but yeah not a blocker. But we do need to implement this as soon as we have time. For the release most of the fixes/features we need to do are around user communication, and this is a feature that is important for the admins (they filter for new activity messages as part of their workflow)
I'll set the priority to low to be addressed after the release
I have concerns about this. Can you please let me talk to ANN and come back to this. Can we pause on this.
@dawn3296 sure, if you later decide we don’t need it, we can close this ticket.
We will change how we do messages in the new release, so this ticket doesn't apply anymore. Closing
We are moving user communication about disputes to Discourse. In order for admins to know there are new user messages, we need a way to display this information in the back office.
The idea is to replace the "User update" status for a "New messages" one. The "New messages" status will be assigned when a user writes a message in the Dispute PM in Discourse, messages from admins won't change the status.
The status will then be changed by an admin after reading the message, which is part of the workflow at the moment.
Notes
A possible solution is to create a plugin that makes a request to a private endpoint in the Dispute tools after creating a comment inside a Dispute PM, to change the status of the Dispute in the tools app.
We need a way to know which PM is a Dispute PM (using custom fields), and a way to access update the dispute status via the tools API. The authentication for the tools endpoint can be a basic
api_token
since this is a system call.Tasks
Acceptance criteria