Open maenujem opened 6 years ago
Yeah, I came here beause it appears subtasks are, unfortunately, implemented differently. I'm guessing this is probably the best bug to watch in hopes that this problem disappears eventually.
Even there is a default alert created, custom alerts are missing in the Android apps. Relative and absolute ones.
Yup, this breaks syncing with Nextcloud.
It gets the tasks, adds a timezone field, and then errors when it tries to sync back.
Yeah, I came here beause it appears subtasks are, unfortunately, implemented differently. I'm guessing this is probably the best bug to watch in hopes that this problem disappears eventually.
Same reason for me, though it's an owncloud instance the sync does not work propperly with.
[ owncloud instead of nextcloud - I guess the server implementations are the same(?) ]
@466
Same reason for me, though it's an owncloud instance the sync does not work propperly with.
Nextcloud forked of from Owncloud some time ago. Would make sense that they share some of the same bugs.
Our major concern is support of RFC 5545, not a particular client/server application. We already have plans to allow configuration of visible fields and their display order. Unfortunately, just like many other features this needs to wait until we have less resources bound in paid projects. Happy to accept PRs and answer questions regarding architecture & design, though.
It would be nice if the android app would have (only) the same features/fields visible for the user and in the same order as the server app in nextcloud. To be more flexible with the android app, there could also be a switch to activate (=hide fields/features not available in nextcloud) compatibility with nextcloud.
Right now the server app has the following fields:
and the android app has the following fields: