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

[Feature request] Assign project to task #4

Open
Heiss opened this issue Jun 23, 2024 · 1 comment
Open

[Feature request] Assign project to task #4

Heiss opened this issue Jun 23, 2024 · 1 comment

Comments

@Heiss
Copy link
Owner

Heiss commented Jun 23, 2024

All tasks need a project in vikunja. So there is a default project selectable in settings. But what, if you want to change it task-specific?

- [ ] this task is in default project [vikunja_id:: 1]
- [ ] this task is in a custom project [vikunja_id:: 1] [vikunja_project:: 3]
- [ ] this task is in a custom project [vikunja_id:: 1] [vikunja_project:: custom_project]

in the second line, you need to know the id. But in line three, there are more errors likely... how should it communicate such cases, if there are no project with such an id or name? Should be created automatically? Or should the user be asked to confirm the creation? Or an error should happen and sync cannot be finished until the user has created the project by himself?

Any opinions?

@amino-8
Copy link

amino-8 commented Oct 17, 2024

I love the plugin and I'm running into an issue where I would love to be able to select a project for a task in obsidian. My opinion is that an error should be thrown and the user should be forced to create the project in vikunja before the plugin will sync.

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