As a beginner I want to get told why buttons are disabled
It's a design principle to hide stuff that is not available. Power users get less distraction this way but beginners search buttons forever.
It's a design principle to disable stuff that is not available. Power users get a tiny bit of distraction but beginners at least can ask them about a button not working.
It's a design principle to be explicit about why stuff doesn't work. The button appears active but when you click it, you get some "Zonk! you not allowed to do this".
I think a mixture of #2 and #3 with grayed out buttons that actually tell you why they are grayed out onClick and onMouseover would help a lot and avoid the pain new user have. This would have avoided iss1072, iss821, iss771 which all go into quite some length about the same button.
Status
Bug is accepted as 'minor ' and the Team needs to fix it.
Comments
Wed, Mar 19, 2014, 22:05 by artjom (PO,T)
As a matter of fact, Kunagi already tells you why you cannot click certain actions. If you hover the item, a tooltip will tell you the reason.
Do you experience something different?
Wed, Mar 19, 2014, 22:27 by Leo Wandersleb
Bold claim ;)
I just clicked on re-estimate for the top priority story on the product backlog and went to the sprint. Now I have a grayed out Pull-next-story-button with no reaction on click and no tooltip.
As (T, SM, PO) I don't see many disabled buttons generally but the issues mentioned in the OP were all regarding that very button and I would guess that a tooltip - while nice in theory - could be extended to some modal window on click with further reading blablabla.
Thu, Mar 20, 2014, 22:29 by artjom (PO,T)
You are right. For the button you mention, the tooltip is missing. We need to add that.
If you want so see the tooltip in action, try accepting a Story as a Team Member (not Product Owner).