A temporary fix to Ditto has been deployed today to work around the issue while a long term solution is implemented.
This essentially opts out of the API change to allow it to continue to work, with the caveat that the ‘team private’ status doesn’t get applied, and is instead created as a private project.
I’ll work on getting something more complete implemented before the final deprecation on the 28th August, I just need some solid time to look at capturing and applying project memberships as a separate entity.
Sorry for not responding earlier. I was out last week. Looks like you’ve come across information about the memberships endpoints which can be used to see which teams or individual users have access to a private project. Anything else I can help with?
In terms of keeping up with API updates, our goal is to inform you directly about any changes like this which may be breaking so you don’t need to periodically read up on things here. We do that through the email addresses we have on file for the user which registered the app (Ditto in this case).
Thank you,
In the current state, I can share my project with the option ‘Open to web’ using the UI, but I cannot get this status using the API due to the deprecation of the public field. Is there any other way I can obtain this information now?
Hi @John_Ervin, have you tried that previously? I don’t believe that’s what public meant in this context. public: true generally means that people in your (Asana) organization could see the project by default. privacy_setting: public_to_workspace is the new equivalent. It does not mean public to the Internet.
I think generating a read-only public link is a separate operation. I’m not aware of support for creating that over the API. If someone else knows of it, maybe they can chime in.
I concur with what @John_Baldo said above: public = true did not mean public to the web, and the UI feature to create a read-only public-to-the-web project view is not currently available via the API.