Bug #11187

Migration to Icedove: Users don't realise how to stop the warning

Added by emmapeel 2016-03-02 15:43:20 . Updated 2016-04-26 09:13:31 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_2.3
Start date:
2016-03-02
Due date:
% Done:

100%

Feature Branch:
doc/11187-claws-mail-persistence
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Email Client
Deliverable for:
268

Description

Users don’t understand that they need to disable persistence of Claws Mail after migration, and they keep clicking on the warning ‘You need to migrate to Icedove’.

The warning (or the migration howto) should mention this step, as some users are still clicking every time they start Icedove.

Subtasks

History

#1 Updated by intrigeri 2016-03-03 14:45:50

  • Category deleted (Continuous Integration)

#2 Updated by intrigeri 2016-03-03 14:46:36

  • Assignee set to sajolida
  • Target version set to Tails_2.3
  • Deliverable for set to 268

sajolida and u, can you please give it a look? I’m not sure if it’s a follow-up on the Claws→Icedove documentation path, that needs to be documented.

#3 Updated by Anonymous 2016-03-04 19:17:49

Hi,

I’m not sure how exactly this warning works. If I remember correctly, that it is shown only when Claws persistence is enabled.

I’m also not sure how this relates to Bug #10742. Is is even possible to disable Claws persistence in that case?

I agree that it could be mentioned in the migration documentation, but I would need to set up quite a test case in order to test this at all. Maybe sajolida already has such a setup?

#4 Updated by sajolida 2016-03-28 10:56:23

  • Status changed from Confirmed to In Progress

Applied in changeset commit:3611ae80dbc90795795ec78893fe706b8ecf6926.

#5 Updated by sajolida 2016-03-29 17:12:13

  • Assignee changed from sajolida to emmapeel
  • QA Check set to Ready for QA
  • Feature Branch set to doc/11187-claws-mail-persistence

Here is a branch for you Emma :)

#6 Updated by emmapeel 2016-03-30 12:36:49

I like the changes, and it would have been good if they were there when we got rid of Claws mail, but I think people will not spot the new information on the howto easily after this time.

Maybe it is better to change the actual error message that appears?

Some users complained after a new release came, I think because they thought the new release will make the message dissapear.

#7 Updated by sajolida 2016-03-31 18:09:53

  • Assignee changed from emmapeel to sajolida
  • Priority changed from Normal to Elevated
  • QA Check changed from Ready for QA to Dev Needed

Good idea! I’ll work on this top then. Hopefully in time for 2.3.

#8 Updated by sajolida 2016-04-07 02:16:11

  • Assignee changed from sajolida to anonym
  • QA Check changed from Dev Needed to Ready for QA

Actually, the warning is not displayed if people go until the end of the
instructions and delete all their Claws Mail data: we check for
~/.claws-mail/accountrc before displaying the warning. So this problem
only occurs for people who didn’t do the whole migration.

Still, I improved the warning to handle this better, see b3fbf4d.

Marking as “Ready for QA” for anonym as this imply some coding and you
and me can’t merge this on our own.

#9 Updated by anonym 2016-04-12 04:54:42

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass

Looks good!

#10 Updated by anonym 2016-04-26 09:13:31

  • Status changed from Fix committed to Resolved