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

Update Task bucket_id #45

Closed
djagoo opened this issue May 1, 2024 · 6 comments
Closed

Update Task bucket_id #45

djagoo opened this issue May 1, 2024 · 6 comments

Comments

@djagoo
Copy link

djagoo commented May 1, 2024

I want to move a task to another project and another bucket based on the bucket it was moved to on the update trigger.

So I created a switch for the 3 bucket_ids in my inbox-project but I cannot update project/bucket_id is there a workaround for this or do I have to wait for it getting implemented?

@kolaente
Copy link
Member

kolaente commented May 1, 2024

Which Vikunja version are you using?

@djagoo
Copy link
Author

djagoo commented May 2, 2024

I am using version 0.23.0. n8n and the n8n-nodes-vikunja are both installed yesterday so the most recent version of them too.

@kolaente
Copy link
Member

kolaente commented May 3, 2024

It sounds like a bug, but I did't try it out. Since the views will change in the next release, the behaviour here needs adjustments as well. I'll keep that in mind while fixing it.

@djagoo
Copy link
Author

djagoo commented May 4, 2024

I explained it very bad sorry. I think it's not a bug but not implemented yet. I want to move a task to another bucket in another project. I just don't find an action in n8n-nodes-vikunja allowing me to do so. Even the action "Update Task" just lets me update for example the title or due date... but not the bucket.

@kolaente
Copy link
Member

kolaente commented Jun 5, 2024

This was implemented in 683cc59. I'll release a new version of this package shortly, but it will contain breaking changes for the next Vikunja release - that means you'll need to run an unstable build until the stable version is released to use it with this node.

@djagoo
Copy link
Author

djagoo commented Jun 5, 2024

Thank you very much, I'll give it a try.

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