+ Add Question

Bug in Todoist Next: right justified text

English is my primarily language, but I sometimes write tasks for myself in Hebrew or Yiddish, both of which go right-to-left. With the new version of Todoist, via the Android app but not desktop, there's a bug. Those tasks are now right-justified, which makes it hard to read when it's mixed between my other tasks that are in English.

Todoist folks, please fix it like it was before, left-justified for English users regardless of the tasks's language.

Thanks!

All responses

Brendon Wadey staff
Replied on Jan 22, 2014 - 01:43 UTC

Hi Yehoshua,

Please clarify, are you saying the task name is on the right hand side of the app, instead of on the left side? Your using it in English, but write certain tasks in Hebrew? Or are you using it in another language?

I can't reproduce this, all my tasks are on the left hand side.

Regards,
Brendon.

Yehoshua Levine premium
Replied on Jan 22, 2014 - 03:36 UTC

Yes, I'm saying the task name is on the right hand side of the app, instead of on the left side. I'm using Todoist in English, but write certain tasks in Hebrew.

If you want a screenshot, lemme know how to send it. I don't see a file upload link on this page.

Thanks!

Brendon Wadey staff
Replied on Jan 22, 2014 - 03:38 UTC

Yehoshua,

I understand the situation. Which version of Android are you running, if you clear the data for the app and log back in, does it still occur?

Thanks,
Brendon.

Yehoshua Levine premium
Replied on Jan 22, 2014 - 03:46 UTC

Android 4.4 on Nexus 4.

I cleared app's data from android settings and logged in again to Todoist. The problem continues.

David Trey staff
Replied on Jan 22, 2014 - 12:58 UTC

Hello Yohoshua,

I have passed this to the developers now, we'll look into it.


Best regards,
David

Brendon Wadey staff
Replied on Jan 22, 2014 - 18:51 UTC

Yohoshua,

This should be fixed in the next release.

Thanks,
Brendon.

Yehoshua Levine premium
Replied on Jan 22, 2014 - 19:01 UTC

Thank you!

Yehoshua Levine premium
Replied on Jan 23, 2014 - 01:00 UTC

It was fixed in today's update. Thank you for being so responsive!