mahara-contributors team mailing list archive

[Kristina Hoeppner <1992119@xxxxxxxxxxxxxxxxxx>]

The problem arises because one action is to confirm to set the status
and the other is to unset the status. We had elected to do the current
implementation to avoid a double negative or long button text, which can
be problematic for translations.

A first step would be to make the titles of each modal unique and then
look into the text and see if it can be made a bit clearer.

** Changed in: mahara
       Status: New => Confirmed

** Changed in: mahara
   Importance: Undecided => Low

** Tags removed: bit
** Tags added: bite-sized

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/1992119

Title:
  Improve UX of sign-off/verify block (Yes|No) confusion

Status in Mahara:
  Confirmed

Bug description:
  For the most part, when modals pop up with a 'Yes' or' No'
  confirmation box, we expect the Yes and No to hold the same actions.

  With the current setup, we need to press 'Yes' when signing-off a page
  and to reverse this action. However, the title of the modal still says
  'Sign-off page' whether we are removing the sign-off state or adding
  it. The description changes, which is helpful, but the logic is
  complex in terms of actions for the users, as they need to unlearn an
  expected response.

  To simplify, this is flow is very error-prone for those who interact
  with the modal.

  ✅ When I see the modal for the first time and click 'Yes', it means I
  want to sign off the page.

  😕 When I see the modal again, later, even though it is already set to
  'Yes', I expect that clicking 'Yes' holds the signed off state, not
  reverse it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1992119/+subscriptions