Task #2007

Bugzilla migration message is not (that) relevant anymore, and could be confusing

Added by Aron Budea over 1 year ago. Updated 9 months ago.

Target version:
Team - Pool
Start date:
Due date:
% Done:


Estimated time:


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 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)?


#1 Updated by Florian Effenberger over 1 year ago

  • Assignee set to Christian Lohmaier
  • Priority changed from Normal to Low
  • Target version set to Pool

#2 Updated by Florian Effenberger about 1 year 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?

#3 Updated by Florian Effenberger 10 months 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

#4 Updated by Xisco Fauli Tarazona 10 months ago

Yes, I'll do it. Sorry for not looking into it before.

#5 Updated by Jean Spiteri 10 months 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.

#6 Updated by Xisco Fauli Tarazona 9 months ago

  • Status changed from New to In Progress

#7 Updated by Xisco Fauli Tarazona 9 months ago

Change done in
cloph should move the change to production soon

#8 Updated by Christian Lohmaier 9 months ago

  • Status changed from In Progress to Resolved

applied the change to repo and live instance

#9 Updated by Florian Effenberger 9 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF