Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better calendar integration and hwo to handle finished tasks #4835

Closed
schiessle opened this issue Jun 21, 2023 · 2 comments
Closed

Better calendar integration and hwo to handle finished tasks #4835

schiessle opened this issue Jun 21, 2023 · 2 comments

Comments

@schiessle
Copy link
Member

I started to use Deck more often to manage my tasks and run into some issues with the calendar integration.

The calendar integration. It is really nice to expose my Deck boards as calendars. But at the moment this tasks show than up on various places:

  • Nextcloud Task app
  • Nextcloud Calendar
  • Desktop/mobile clients which sync the calendar

But all have in common that I can not complete / tick-off a task. Which means that I get notified forever until I go to deck and archive or delete it. It would be nice if we could tick-off on the various clients the tasks like regular caldav tasks and translate it server side to a useful action.

... This lead me to the second part:

As mentioned before, the only way to complete a task is to archive it or delete it. It would be nice to have a logic like, everything moved to a "Done" column is considered as done. This way we could move ticked-off tasks to the done column and they would no longer show up in the external clients as open tasks and also not in "upcoming cards" of Deck.

Another option would be to archive tasks ticked-off with a client and maybe give them a additional label like "completed" so that if the user looks later at the archived card they know why the card was archived.

Or a third option?

@stefan-niedermann
Copy link
Member

stefan-niedermann commented Jun 21, 2023

And again: This all is caused by a missing done state and has been discussed so many times: #534 (There even exists a PR).

Additionally: For your use case there are further issues which need to be fixed, like #2399

However, it is everything here. It has been documented and discussed in the growing number of issues. Many times... Sorry, I don't want to sound harsh, but it is quite hard to keep the issue tracker clean, so please, as we all tell the community and users: Search for existing issues before opening duplicate ones 😉

@schiessle
Copy link
Member Author

@stefan-niedermann I just didn't found the other tickets 🙈 Let's close this one than and follow up on the existing one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants