Feature #15578

Explain better what removing a package means

Added by sajolida 2018-05-05 15:22:18 . Updated 2018-08-09 20:23:21 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.9
Start date:
2018-05-05
Due date:
% Done:

100%

Feature Branch:
feature/14594-asp-gui
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Additional Software Packages
Deliverable for:

Description

During the user testing of the Additional Software beta:

  • 2 participants hesitated before clicking the [X] button.
  • After clicking “Remove” in the confirmation dialog, 1 participent still doubted whether removing meant uninstalling or deleting. Actually, it means something else :)

We could:

  • Add a tooltip on the [X] button.
  • Explain a bit more in the confirmation dialog.

Subtasks

History

#1 Updated by sajolida 2018-06-05 15:48:41

  • Assignee set to sajolida
  • Parent task changed from Feature #14592 to Bug #15567
  • Affected tool set to Additional Software Packages

We’ll try to fix that but it’s not a blocker to deliver SponsorW_2017.

Next step: I should propose a wording for a tooltip.

#2 Updated by sajolida 2018-07-16 13:54:21

  • Target version set to Tails_3.9

#3 Updated by sajolida 2018-07-17 13:59:28

  • Assignee changed from sajolida to alant
  • Type of work changed from User interface design to Code

Proposed wording for the tooltip:

Stop installing $package automatically

If it’s too complicated to include the name of the package:

Stop installing automatically

Rationale: we’re not explaining anywhere what removing the package from the list really means. “Removing” means “stop installing automatically” (but not “deleting from persistence” or “uninstalling immediately”, for example). This was only a slight problem for P3 who hesitated a second to click on the cross button. So let’s keep the phrasing that we already have in the confirmation dialog (this would be too late for P3 anyway) and be a bit more explict in the tooltip, who only people who will hesitate will see.

#4 Updated by alant 2018-07-27 10:27:31

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 30
  • QA Check set to Ready for QA
  • Feature Branch set to feature/14594-asp-gui

Implemented in feature/14594-asp-gui, to be tested in real ISO.

#5 Updated by alant 2018-07-27 11:06:05

  • Assignee changed from alant to sajolida
  • QA Check changed from Ready for QA to Info Needed

Shouldn’t we also add in the confurmation dialog “Remove $package from your additional software? This will stop installing the package automatically.” or something similar?

#6 Updated by sajolida 2018-07-28 16:39:52

  • Assignee changed from sajolida to alant
  • QA Check changed from Info Needed to Dev Needed

Yeap, that would be great.

#7 Updated by alant 2018-07-30 22:45:07

  • % Done changed from 30 to 60
  • QA Check changed from Dev Needed to Ready for QA

#8 Updated by Anonymous 2018-08-07 13:14:08

  • Assignee changed from alant to sajolida

I’m assigning this to sajolida, as you probably meant to do when marking this as ready for QA? If not, please reassing back to you. Note that the deadline to get this merged is in one week!

#9 Updated by sajolida 2018-08-08 18:27:55

  • Assignee changed from sajolida to alant

I’m happy with what I see in the Git log.

u: I think that sometimes Alan assigns stuff as “Ready for QA” to himself until he tests his changes.

Alan: if you tested this already please mark it as “Fix committed”.

#10 Updated by intrigeri 2018-08-09 05:54:00

> Alan assigns stuff as “Ready for QA” to himself until he tests his changes.

Indeed. At least anonym and I do the same pretty often. And incidentally (or on purpose) this enables ISO reproducibility testing on Jenkins :)

#11 Updated by alant 2018-08-09 20:23:21

  • Status changed from In Progress to Resolved
  • Assignee deleted (alant)
  • % Done changed from 60 to 100
  • QA Check changed from Ready for QA to Pass