-
Notifications
You must be signed in to change notification settings - Fork 283
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
Attach due date to cards #106
Comments
@juliushaertl if you approve my suggestion - so i can implement it. |
I am currently implementing a basic attachment api that will allow any type of data being attached to cards. That way we can also add dates, e.g. a due date to the card. I should have something testable ready by the end of this week. |
I'll keep you updated on that, so you can do the due date implementation if you want. 😉 |
Is attachments really easier / more correct way to go than simply add another field ? |
but adding the date field to a single card should also mean creating a calendar (.ics) for the parent board, right? Something that can be handed over to the CalDAV and Calendar app. |
I thought about that and it makes sense to me, also in terms of sorting/filtering from the database.
Different issue, but yes, this is how this should be in the future. |
@juliushaertl yes...sure! I'm waiting for your "big release" ;) |
Linking cards with the tasks in SabreDav would enable using existing functionality for this and all the other features of the Nextcloud tasks - perhaps most easily done by just "including" the related task settings from the task app in the card properties when card is linked to a task. Further integration with tasks could include connecting tables with task lists (i.e. the CalDAV calendars), making the relations and coherent across the ... "board". :) CalDav also supports adding unlimited custom fields specific to Nextcloud so that special features unique to NC can be promoted without breaking compatibility with other clients. |
Sure, linking cards to existing tasks/events makes sense, but i think there are some issues:
I'd prefer to go for a dedicated duedate per card for now. My initial thought was to expose each card as a separate task, into a "calendar" for each board. See #15 for the dav integration thoughts. |
what do you think about a "exp. date" field? card should be highlighted (icon or background) when the date is exceeded.
The text was updated successfully, but these errors were encountered: