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

Add menu option to interrupt a contact #3905

Merged
merged 8 commits into from
Jul 26, 2022
Merged

Add menu option to interrupt a contact #3905

merged 8 commits into from
Jul 26, 2022

Conversation

rowanseymour
Copy link
Member

@rowanseymour rowanseymour commented Jul 21, 2022

@rowanseymour
Copy link
Member Author

Not sure about this because the interrupt action will be asynchronous... maybe for the single contact case we should have a endpoint to do it synchronously so the user sees the current flow badge disappear after they click this.

@codecov
Copy link

codecov bot commented Jul 21, 2022

Codecov Report

Merging #3905 (75b7838) into main (27324dd) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main     #3905   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          394       394           
  Lines        26380     26397   +17     
=========================================
+ Hits         26380     26397   +17     
Impacted Files Coverage Δ
temba/contacts/models.py 100.00% <100.00%> (ø)
temba/contacts/views.py 100.00% <100.00%> (ø)
temba/mailroom/client.py 100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us.

@ericnewcomer
Copy link
Member

I think we definitely want to start with a sync endpoint for this.

@rowanseymour rowanseymour marked this pull request as ready for review July 22, 2022 20:15
@@ -618,6 +619,7 @@
"contacts.contact_export",
"contacts.contact_filter",
"contacts.contact_history",
"contacts.contact_interrupt",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Editors should also be allowed as they can start flows as well

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty weird that editors start flows. I wish we had a better line between them and admins. I think the only real difference is user management and billing.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correct, everything else is the same except user management and billing

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that's true - editors don't have access to much of workspace administration. I also don't think it would be particularly useful to have a role which can edit flows but not use them.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've given the perm to editors and honestly I think we should expand that to agents too when this stuff is accessible from the ticket view because they'll probably need to be the people who pull contacts out of flows.

@rowanseymour rowanseymour requested a review from norkans7 July 26, 2022 14:34
@rowanseymour rowanseymour merged commit 7e56b54 into main Jul 26, 2022
@rowanseymour rowanseymour deleted the contact_interrupt branch July 26, 2022 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants