Replies: 1 comment 4 replies
-
|
GitHub supports due dates through milestones. To assign a due date to an issue, you should create a milestone with a due date and associate it with the issue. I haven’t implemented this functionality directly in the application because I don’t see a strong need for it at the moment. The GitHub provider was added for one specific purpose: to display issues from a project. That said, if you have a different perspective or believe the provider should support additional capabilities (such as more filtering options, for example), please create an issue outlining the required features. Also, feel free to reply if I’ve misunderstood your request - I’m happy to clarify or adjust! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I stumbled across this project and am intrigued. As a user of many of the providers, this seems like a good central place for seeing the relevant tasks.
Currently, I use Obsidian with fine-grained dates: start, due scheduled. In Obsidian, I have queries to filter the relevant tasks. When bringing Obsidian together with different providers, this seems to break down.
Right now, many tasks are simply scheduled, not necessarily due. But providers like github issues don't have that distinction.
How would you suggest to resolve this?
Beta Was this translation helpful? Give feedback.
All reactions