[Trunk/7.0] Naming issue on cancel button of project issue

I find that I click the wrong one maybe 50% of the time. It is really annoying.

Hello Dainel,

I have check your issue but this is not a issue.
Done and Cancel is a workflow button. so state is canceled (this is expected).
when you did not changes so please click Discard.

Thanks

Setting status to 'Confirmed'. This was already an issue with the stock workflow in earlier versions for our customer and in that case the "Cancel" button was on the other end of the form from the "Save" button. They are now next to each other.

Farid, how can you disregard a usability issue like this? Usability is touted as the fifth main reason for upgrading to OpenERP 7 (http://v6.openerp.com/node/1316)

Hello Stefan,

Ok, Understand. We can do the same thing on Project Issue same as done on Task for avoiding the confusion.

On project task we have a same button for cancel task, We have used a "Cancel Task'" name on button.
So we have to done same thing for project issue, Changed the string of cancel button on issue as "Cancel Issue".

Consider as a usability issue and assign to addons.

Thank you

Hi Amit,

thank you for understanding! There may be other views with the same problem but I guess we can file separate issues for them.

Cheers,
Stefan.

Hallo Stefan,

Yes, you are correct. You can post a one bug report for all issue as a usability.

We will fix all on one bug.

dank u..!!

Hello,

           For 7.0 it has been Fixed in https://code.launchpad.net/~openerp-dev/openobject-addons/7.0-bug-1103426-hip
           Revno: 8610
           Revision ID: <email address hidden>

Thanks,
hip

The wording issue between "cancel" (action workflow) and button "cancel" in a dialog box which users are accustomed to use to close the dialog without any action being performed is critical. I had customers waist hours because of this before they learned (on oerp 6.1) to distrust any button with "cancel" as a label and use the "X" window button to close such dialogs.

IMO, this issue cannot be solved by moving the "cancel" workflow action to a different place : in some UI, the dialog cancel button is on the left, in others it's on the right... The correct solution is rather to use a different verb altogether for the workflow action. It must be different from "cancel" (or "Annuler" in French) because these are identified to do something different by users.

Possible english verbs include:

* void
* invalidate
* withdraw

"Invalidate" sounds excellent. Another possibility might be "Inactivate".

Another suggestion is to place it's button on the far right, after the `statusbar`widget.
That shouldn't be difficult, but right now the statusbar CSS forces it to be the right-most element, so that buttons after it are presented in the next line.

Correction landed on 7.0 addons at revision 8739 rev-id: <email address hidden>

Thanks for reporting!

Note: I've seen a lot of similar buttons in form views, I'll search the bugs for similar bug reports and/or fix them now.

While these words are fun for a brainstorming session (I liked void, I
would certainly not know what to do with it...), they do not add clarity
in a real life situation. We need usual wording, used everywhere, no
user is dedicated to Openerp only.

Cancel means close without saving almost everywhere. like save | cancel,
or Save | close, there is also OK |Cancel, but mostly in a dialogue.

I think that the "faulty" action is "set object to Cancelled status";
this shall be addressed. Why not just use something like I just wrote:

Set [object] to cancelled state/status

I would also avoid "close" and "cancel" put together as they are still
confusing.

thank you,
Bogdan

On 25. 01. 13 12:36, Daniel Reis (SECURITAS SA) wrote:
> "Invalidate" sounds excellent. Another possibility might be
> "Inactivate".
>
> Another suggestion is to place it's button on the far right, after the `statusbar`widget.
> That shouldn't be difficult, but right now the statusbar CSS forces it to be the right-most element, so that buttons after it are presented in the next line.
>

FYI, a series of additional fixes to similar buttons in all addons has now landed in the 7.0 branch at revision 8795 (rev-id: <email address hidden>). The translation templates will be updated soon.