If it ain't broke...

7 Responses

1. Pro Garrett Dimon

   With some slight tweaks to the existing way of doing it, it doesn't seem all that bad. This way we only need a single "update" button at the bottom.

   One click status updates will just need to be handled some other way. Full context (and very rough comp) over on Mocksup.

   over 1 year ago

2. Pro Zach Inglis

   This is much more in the style of your work and the rest of the application. I think it's workflows like this that make your work/the app great.

   over 1 year ago

3. Pro Garrett Dimon

   I agree that it works. This just has the unfortunate side effect of requiring 2 clicks instead of one when just want to close an issue, but I think that's a separate problem that I'll have to solve some other way, or maybe not at all. :)

   Thanks!

   over 1 year ago

4. Pro Kyle Meyer

   I loved reading about the arrow solution in this shot way back in the day—still as elegant as ever and one of my favorite solutions. Nice work!

   over 1 year ago

5. Pro Matthew Anderson

   Happy you decided to stick with this, Garrett. The flow of the radio buttons is much more suggestive and easier to follow. I think the instant-close issue might be better solved from a different (previous) screen entirely.

   over 1 year ago

6. Pro Rich Thornett

   I'm the kind of person who actually prefers that there is some sort of comment associated with every status change. So I think the status-explanation-save workflow feels completely natural, even if a click could have been saved; status and save are orthogonal concepts IMO. Glad you came back to the original design.

   over 1 year ago

7. Pro Garrett Dimon

   Rich - I agree with you about adding a comment to everything. However, I also notice that in a lot of stuff it's been overkill. I think with some additional polishing, this one will definitely work.

   over 1 year ago