Hi all -
Asana has recently started deprecating task-sections in favor of “column-sections” (Build an app with Asana) - this is good in the long run, but it’s broken my custom Asana2Go report in the meantime.
Anybody got any solutions to pull through section names for tasks - I was using the below:
{{#if memberships.0.section.id}}
{{memberships.0.section.name}}: {{name}}
{{else}}
{{name}}
{{/if}}
@lpb looks like you are needed
Hi @Kyle_Johnson and thanks @James_Carl. Kyle, could you send me an export of your custom format (Wrench menu > export to create the .json file) and I’ll have a look for you tomorrow late afternoon or evening (I’m away until then).
Thanks,
Larry
@Joe_Trollo, It looks like the tasks.memberships array section property is no longer getting valued for list projects. I don’t see any specific mention in blog posts or API docs of that being part of the deprecation but I imagine now it must be. When will it be valued again–only 1) after lists/boards is rolled out, and 2) also only for migrated projects? Can you give a rough idea how close (1) is since this deprecation seems to have broken Asana2Go again without notice.
Also, on a few browsers (Chrome/Win/Incognito, Firefox/Win) the formatting of the page Build an app with Asana is broken–the tabular layout ends after the entry for external and all the remaining properties are incorrectly formatted.
Thanks,
Larry
Yikes! Is this with the new_sections header enabled or not enabled?
@Phil_Seeman, new_sections is enabled.
@lpb, the behavior you’re seeing is intended. When you have new_sections enabled, anytime the API says “section” we mean a real column-section. List-view projects have no column-sections in them, so any membership for a task in a list-view project will have null for the section. When the project is migrated and a proper column-section is created to replace the separator, then the membership will contain a section again.
I don’t have a concrete timeline yet, but the current estimates are that customers will be receiving migrated projects within the next month or so. I’ll be meeting with the team in charge of the deprecation later today and will have more information then, which I’ll share on the official post.
Thanks for the notice about the docs. We noticed it too and are working on fixing it. Sorry for the mess in the meantime!
Thanks, @Joe_Trollo, for the info, which was as I expected after seeing this, but I didn’t realize initially that it was expected since some API changes were enumerated and in my 500 readings (!) of your posts I didn’t catch that this one was affected or expected there’d be notice when it specifically was changed.
Anyway, Asana2Go will have to wait for this to start working again in order for this part to function again.
Re:
I thought customers choose in the UI when to migrate a project until some future date on which they’ll start being converted automatically, but what you write sounds more passive. Is it still up to the customer, project-by-project? Or what did you mean?
Thanks for the quick reply, as usual!
@Kyle_Johnson, Sorry, I think we’re out of luck until it starts working automatically again.
Thanks,
Larry
@lpb Thanks, no worries. Not critical for us. We can wait. Thanks for looking into it.
@lpb thanks for reporting the broken table in the tasks documentation! We had a bug slip through that broke the formatting, but we’ve prepared a fix and you should see it corrected in our docs very soon!
The roll-out plan will be different than we thought it would be when I last updated the main post. Sometime next week when I have a more concrete timeline, I’ll be posting a new update with the new plan. Sorry I don’t have more information to share right now.
Thanks, @Joe_Trollo. And I just wanted to say that I appreciate that you shared this info with the proviso that it could change and did. I still like getting more/earlier info and totally understand the consequence.