Task #2007
closedBugzilla migration message is not (that) relevant anymore, and could be confusing
0%
Description
If you enter an invalid login/password, you get an error page:
-in black, on a red frame: "The login or password you entered is not valid."
-in black, on a white rectangle inside red frame: "We migrated all of the LibreOffice bugs from freedesktop.org to our own TDF Bugzilla on Saturday, January 24th, 2015.
Have you reset your password yet?"
I got an e-mail from someone who was confused by this second message. Since January 24th, 2015 was long ago, can the message be removed?
Or if we want to keep it for some more time, can it be moved below the red box, and the size be reduced (since it's definitely less important now)?
Updated by Florian Effenberger about 8 years ago
- Assignee set to Christian Lohmaier
- Priority changed from Normal to Low
- Target version set to Pool
Updated by Florian Effenberger almost 8 years ago
- Assignee changed from Christian Lohmaier to Xisco Fauli Tarazona
- Priority changed from Low to Normal
As discussed with Björn, Bugzilla to be handled by Xisco
Xisco, is this something you can handle, or do we need Guilhem's assistance?
Updated by Florian Effenberger over 7 years ago
Ping? ;-)
Xisco, is this still relevant and something you can quickly fix? If not we involve Guilhem, I think it's just updating one template
Updated by Xisco Fauli Tarazona over 7 years ago
Yes, I'll do it. Sorry for not looking into it before.
Updated by Jean Spiteri over 7 years ago
What about replacing the migration message with a message on the password rules? Something that reminds the user that a capital or a number is needed (don't know the exact rule). That could help the user remember the password if he forgot it.
Updated by Xisco Fauli Tarazona over 7 years ago
- Status changed from New to In Progress
Updated by Xisco Fauli Tarazona over 7 years ago
Change done in https://bugzilla-test.documentfoundation.org/
cloph should move the change to production soon
Updated by Christian Lohmaier over 7 years ago
- Status changed from In Progress to Resolved
applied the change to repo and live instance
Updated by Florian Effenberger over 7 years ago
- Status changed from Resolved to Closed