Editing a message should not deposit you back at "All Messages"
|
|
I just wanted to bring attention to what I think is a new behavior in Basecamp. I go to the detail view of a message, then edit the message and click “Save changes”. Until recently, doing that would take you back to page you came from (the detail view for the message) so that you could review what you’ve posted. Now, you seem to be deposited at the “All Messages” screen. To see how the message turned out after you’ve edited it, you have to now navigate back to the message. Even if you navigate to a certain category and then click “edit” without going into the detail view of a message, after editing the message, you end up at “All Messages” and not in the category you had just come from. If you click “Back”, you go back to the edit message screen that appears to be processing the post. As a project manager, I, like many others, spend a good deal of time updating the original message to reflect the current status of a discussion or tasks. This new behavior makes things much more time consuming. I don’t know if this was deliberate decision or if it was a result of recent upgrades to Basecamp. I just want to cast a strong vote to return to the much more user-friendly approach of returning the user to the view they came from after editing. |
|
|
I’d noticed that and couldn’t remember if it was ever any different! |
|
|
I had the same reaction. I think that’s because the original behavior (and I admit, I don’t recall exactly what it was) felt very natural. The current behavior feels a little jarring. |
|
|
We’ll check that out. You should be returned to the message you were editing, and not a list of messages, when you’re done. |
|
|
I’m glad this issue had been posted, I came today to mention it as well. Any progress made? |
|
|
I know better than to ask 37s for a time frame regarding a modification, but after two months, I just have to re-request this very important fix. Being redirected to “All Messages” after editing a message continues to prove time-consuming and frustrating. Pretty please! |
|
|
Just curious who else out there has noticed this problem. At first glance, it’s a minor usability issue, but if you edit messages frequently to show current status of a discussion or task detail, then it becomes quite the hassle. Here’s hoping that they change it back to how it used to function (take user directly to updated message when done editing). |
|
|
I’ve found and fixed this problem now. We’ll deploy the solution shortly. |
|
|
Excellent news. Thank you! This was one of those things that wasn’t really an issue worth complaining about but could get a bit annoying after a while. It’s good to see the 37S team consider the small things as well as the big issues. It makes for a much better experience with the product. |
|
|
Not sure if you’ve deployed this yet but we’re still experiencing the problem. |
|
|
Looks like it’s now fixed. Thank you so much for taking care of this!! This is more helpful than you know. |
|
|
Was this fixed? We still get the behavior as described in the original post. |
