As part of our ongoing efforts to better communicate what’s going on at Atlassian with you, we are standardizing how we communicate technical changes to our products using community.developer.atlassian.com (CDAC).
We now have subcategories in the product categories that are specifically for announcements from Atlassians, e.g. Jira Cloud Announcements. You may be able to comment on the post depending on whether the poster is looking for feedback or not. You’ll see we have retroactively moved our old announcements into these new subcategories.
These subcategories will also augment the changelogs on developer.atlassian.com (DAC), where we will cross post each change from DAC to CDAC. The reason we are doing this is so that you can subscribe to notifications about changes, using the Subscribe button at the top right corner of the CDAC category.
Could you please outline the rationale behind this initiative? Searching for important information on CDAC is a nightmare for vendors. E.g. recent changes to Security and New Partner programs are perfect patterns of how NOT to communicate on upcoming changes. Literally most of vendors were completely unaware, lost and unprepared for them. Instead of having a single source of truth, we all were browsing numerous random threads, comments, tickets, etc. And btw we are still figuring out how to deal with this new reality.
And instead of learning this lesson, Atlassian is pushing CDAC approach even harder. Why?..
I hope we all understand that changes to an Enterprise ecosystem of a huge public company should be posted in a more official, more easy to read and easy to subscribe channel. Ideally a public Confluence blog with links to docs and manuals plus newsletter subscription that will be automatically on for every vendor. Something like Partners portal. And yes, it’s already there.
Our intention is to make CDAC the single source of truth, or more accurately, the source that ties all the other sources together. We recognize that there are many places where you will go to consume more information (DAC, Jira boards, Trello boards, etc.) because those are the tools the internal teams use to update their information. The intention is to make CDAC the one place you need to check to see if there are updates to those sources with information that impact you.
This is our official, easy to read, easy to subscribe channel. We have the developer blog and have used it in the past to communicate critical changes, but there were several problems with that approach: 1) it requires special permission to access, and therefore is not easily adopted internally, 2) there is no ability to comment or interact with the content (I think you’ll agree that is quite important ), and 3) a blog is by nature a marketing tool, which doesn’t fit the use case here.
CDAC is the most democratic, easy to access channel that we have (you don’t even need to login to see the content), which is important for Atlassians as well as the entire developer community. The Partner Portal will never be open to all developers, and Slack doesn’t scale.
In my view the problem is not CDAC, but rather that we haven’t used CDAC to its full potential. It’s the content management practices which make or break the tool, and point taken, we have not done the best job there. That’s why it’s part of my job to work with all our internal teams and make this part of their processes. I completely understand why you are skeptical now, but please give it time, allow us to get better at using CDAC consistently, and we can revist later.
I think this is the crux of the issue, and it’s great to see you acknowledge that.
Part of the problem is that while a lot of valuable content exists here in the form of Q&A, the A part is rarely curated or rolled up by Atlassian into FAQs or other documentation. Lots of critical information is buried in CDAC in easy to miss places. A better model for the Q&A aspect of the apparent intent for CDAC might be something like Confluence Questions or a Stack Exchange site, and failing that, some deliberate, manual curation of the Q&A by Atlassian.
Another problem with CDAC is simply the lack of timely participation by Atlassians. Much of the time it feels like Atlassians simply throw information over the wall into CDAC and never return to engage with partners on the topics they create, or when they do the sense of urgency partners bring to bear is not reciprocated. It doesn’t feel like it’s anyone’s actual job to make sure that questions are answered in a timely fashion like you’d get from a support queue with SLAs. Even when a conversation is started successfully, threads go cold mid-conversation and followups miss important deadlines. There seems to be a low level of accountability from Atlassians for their role in making the CDAC strategy effective.
CDAC itself is excellent software, at least for holding basic conversations. I think that not only is being ineffectively applied, but it’s perhaps also being asked to do more than it’s designed for.
Anyway, best of luck improving on these and other issues – I hope you are successful! I look forward to seeing the results of continued integration with teams across Atlassian.
Sorry Katrina, that’s not what I meant. I am able to access those topics when logged in via the website, but how do I subscribe to those via Slack? How do I authenticate in Slack to subscribe to the private topics?
You might want to look into your subscription engine, though. When I subscribed to new topics in the channels you mentioned, I received 60 emails containing notifications of old posts from as early as 2018…
That includes the in-app subscription announcement. Right now CDAC is kinda broken for me as I’m signing up for these announcement categories (I’m hoping though that it will go away naturally).
Is it possible to get the Jira announcement categories nested? (And have Cloud nested underneath itself etc). From a usability - having to search through 100 categories will be an area that can be improved…
That’s the thing. We still have multiple sources, and there’s literally no way to check if all updates are here. For instance, there’s a partners only updates that are posted in closed Partners section here on CDAC or in the Partners’ Confluence.
Most critical/important announcements are made in those two areas, mentioned above. They have no public access, so the sentence above is not quite true. And yes, most commonly we are restricted by NDA to disclose anything posted there. Please keep in mind.
I’ve personally posted comments under blog posts in the Partner’s Confluence. No Atlassian response though, some likes, but still - Confluence allows commenting, that one of core functionalities out there.
Sure thing, do your best. But there’s one thing mentioned already quite a few times. For some reason, Atlassian is not used to listen to vendors. Instead of having an open conversation about issues we have and ways they can be improved, we are facing these announcement posts about something new. They are full of joy, happiness and smiles, they are to fix issues you think we have. And I’m 100% ok with being positive, but after years of being Marketplace vendor I would love if you start your new cool shiny thing with a little research. May be even talking to vendor council.
E.g. I’ve pointed to a very specific case with new security program many of us recently faced. But it seems like you decided to skip on that. And that is exactly what actually makes me feel skeptic about this initiative. I hope I’m wrong though.