Repository navigation
Replies: 3 comments
|
Just put it in the three dots along with all the other thread actions |
|
+1, I hit this every day. I keep a lot of threads open and go through them on the phone. When one is done I can't settle it from inside, and after going back I'm not always sure which row it was, so I don't want to settle the wrong one. Proposal: Settle in the open thread header on iOS and Android, back to the list when it succeeds, stay in the thread with the error when it fails. It reuses the existing settle action, no server change. @maria-rcks would this scope work for you? I can open a PR |
|
+1. I triage threads on my phone and would use this every day. Settling from inside the open thread and landing back on the list would make it a one-tap action, with no hunting for the right row afterward. The scope @CodeWarriorr proposed (Settle in the thread header on iOS and Android, back to the list on success, stay with the error on failure) covers what I need. |
Uh oh!
There was an error while loading. Please reload this page.
Problem
When I finish reading a conversation in the T3 Code mobile app, I want to settle it directly from the open thread and return to the thread list. Having to leave the conversation first and then find the same thread in the list adds friction to a simple "I'm done with this" action.
The interaction I have in mind is Gmail's archive action inside an open email conversation: tap the action, and you're back in the inbox, ready to pick the next item.
Requested behavior
A button in the thread header would make this easy to reach. An action in the thread's overflow menu would also work; the exact placement is open to maintainer preference.
Please use the existing Settle behavior. The Gmail analogy describes the interaction, rather than requesting T3's separate Archive action. The conversation should remain accessible through the existing settled-thread flow.
If settlement fails, stay in the conversation and show the error.
Related
#16090 describes a related navigation problem after settling on web/desktop. This request is specifically for an action in the mobile conversation view that returns to the thread list.
All reactions