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

Attach due date to cards #106

Closed
artemanufrij opened this issue Apr 30, 2017 · 9 comments
Closed

Attach due date to cards #106

artemanufrij opened this issue Apr 30, 2017 · 9 comments
Assignees
Milestone

Comments

@artemanufrij
Copy link
Member

what do you think about a "exp. date" field? card should be highlighted (icon or background) when the date is exceeded.

@artemanufrij
Copy link
Member Author

@juliushaertl if you approve my suggestion - so i can implement it.

@juliusknorr
Copy link
Member

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.

@juliusknorr
Copy link
Member

I'll keep you updated on that, so you can do the due date implementation if you want. 😉

@juliusknorr juliusknorr changed the title [feature request] add a new field: exp. date Attach due date to cards May 1, 2017
@juliusknorr juliusknorr added this to the 0.2.0 milestone May 1, 2017
@x9t9
Copy link
Collaborator

x9t9 commented May 9, 2017

Is attachments really easier / more correct way to go than simply add another field ?
I think that due date is an inherited property of a task which is part of it's definition ( Just like title or description ) , and as such it should be handled , as opposed to attachments that can be seen more of a way to extend the "optional" properties or annexed Info related to the nature of the task .

@pixelipo
Copy link
Contributor

pixelipo commented May 10, 2017

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.

@juliusknorr
Copy link
Member

Is attachments really easier / more correct way to go than simply add another field ?

I thought about that and it makes sense to me, also in terms of sorting/filtering from the database.
@artemanufrij Are you still open for implementing this one?

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.

Different issue, but yes, this is how this should be in the future.

@artemanufrij
Copy link
Member Author

@juliushaertl yes...sure! I'm waiting for your "big release" ;)

@bjornnorman
Copy link
Collaborator

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.

@juliusknorr
Copy link
Member

Sure, linking cards to existing tasks/events makes sense, but i think there are some issues:

  • Permissions of CalDAV calendars differ from the boards permissions
  • What due date will be shown when multiple tasks are linked

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.

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

No branches or pull requests

5 participants