Hi,
Not sure if im missing somthing. I tried to create a subtask with the field is_rendered_as_separator: true but that didnt create a subtask-section. Is it possible at this moment to create separators on a subtask or should that be created on a section endpoint to the apI?
Thanks!
@Jonas_O, I havenât tried setting the field myself (only getting it), but a quick possible cause to confirm: Are you positive you have enabled the deprecation header when trying this?
@Joe_Trollo - Thank you for keeping us up to date. However, I still have not received an answer to how to sort sections within the new Sections framework. We have a process which would create Sections in Alphabetical order and then tasks under the correct section. The sorting of the sections is critical to our workflow under this project.
We currently are able to do this by using the Task API on projects which have not been converted to the new Sections interface. The documentation for new Sections does not allow for sorting. Additionally, I created a Board Project and attempted to use the âsectionâ and âinsert_afterâ option (both listed under the task API and were referenced ealier in this thread as possible options) when creating a new section but had no success.
Please provide thoughts on how to insert of Sections in Alphabetical order with the new Sections API.
If this is not an option, it will break our current workflow and make Asana unusable.
Thanks for your feedback!
Hi @Benjamin_Ragan,
Did you try this endpoint with the before_section or after_section parameter?
@Phil_Seeman - I tried âafter_sectionâ. It does not appear to work when creating a new Section. This appears to move a section after the Section has been created. This would require 2 calls, which can be done, but is not ideal.
If I am missing something, please let me know.
I havenât tried it myself but there is a specific example on that page of adding a new section and including before_section in the insert call (itâs under âAdd or move a section in a projectâ); maybe try that to follow that example and see if you can get that to work?
Thank you for your feedback. I agree there is a heading Add or move a section in a project, but the example assumes the call already has a gid for the section.
curl -H "Authorization: Bearer <personal_access_token>" \
https://app.asana.com/api/1.0/projects/1331/sections/insert \
--data-urlencode "section=2001" \
--data-urlencode "before_section=2002"
This would indicate the section was already created prior to adding to a project or moving within a project.
Any other suggestions, other than making two separate calls API calls (Create the Section then Move the section)âŚ
Again, thank you for your help.
Good point! Time to call in the cavalry.
@Joe_Trollo @Matt_Bramlage @Jeff_Schneider: is there a way to add a new section in a particular location within a projectâs sections, or do you need to add it first, and then do a second call to place it?
Hi @Benjamin_Ragan, the API should support insert_before and insert_after when creating a section, but upon inspecting our code I found a bug which was ignoring these parameters. The fix should be deployed in another day or so, after which both POST /sections and POST /projects/<project-id>/sections will accept insert_before and insert_after.
Hi @Nikolay_Yanev, the API does not permit migrating projectsâmigration will be triggered by users in the web app on a per-project basis. This is not yet available to users, though, and we do not yet have a timeline for rolling it out.