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

Allow updateTask to handle updating of the tasks assigned project ID for moving tasks between projects #265

Closed
StevenStavrakis opened this issue Jan 15, 2025 · 8 comments
Labels
enhancement New feature or request

Comments

@StevenStavrakis
Copy link

Enhancement description

Based on the current SDK docs, there is no way to update the projectId of a particular

The problem it solves

Self-explanatory

Alternatives

Currently, moving a task to a project after creation requires re-creation and deletion.

Use case / screenshots

n/a

Additional information

n/a

@StevenStavrakis StevenStavrakis added the enhancement New feature or request label Jan 15, 2025
@scottlovegrove
Copy link
Contributor

@PotHix I've just tried the REST API and providing a different project_id when updating a task and I get a 400 response with At least one of supported fields should be set and non-empty. Should it be possible to move tasks via the REST API?

@PotHix
Copy link
Member

PotHix commented Jan 16, 2025

Should it be possible to move tasks via the REST API?

No, the move is not implemented in the REST API.

For the record, moving internally is a more intricate operation, it's not just changing the ID, that's why it was not implemented yet. It's something we have in the roadmap, but will not make the cut for the next API version.

@scottlovegrove
Copy link
Contributor

@PotHix Thanks for the info.

@StevenStavrakis Unfortunately, for now, you would need to make use of the Sync API in order to move an item, which would be done outside of this SDK.

@scottlovegrove scottlovegrove closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2025
@StevenStavrakis
Copy link
Author

Thanks for looking into this. Is there a reason the SDK doesn't support the Sync API? As in any security or LTS considerations I should be accounting for as I continue with my project.

@scottlovegrove
Copy link
Contributor

@StevenStavrakis We are actually working towards this and the next version of the SDK will be using the Sync API under the hood.

@StevenStavrakis
Copy link
Author

@scottlovegrove Thanks for the info, Scott. I know it's never a great question, but is there any kind of timeline on that? I'm currently working on a project that depends heavily on the SDK and the feature I've mentioned. If something is coming down the pipeline in the next month or two, I think I'd rather wait until then (along with feature relating to the new deadline field)

@scottlovegrove
Copy link
Contributor

I haven't forgotten about this @StevenStavrakis, there are discussions going on at the moment and I want to make sure I give you the right information. Please bear with me.

@scottlovegrove
Copy link
Contributor

@StevenStavrakis I have added the functionality into the SDK to allow you to move tasks using it, but it will only be in v4 of the SDK. We are still a few weeks away from that release being final, however, you are able to try it out using the pre-release versions, in this case, you would need v4.0.0-alpha.3. Do please give this a try if you are able to, and let us know if you have any issues/feedback.

Thanks for your patience in this matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants