Can you please clarify your migration algorithm/policy?

Hi Team,

According to Announcing the new Atlassian Community, "all answered usage and admin questions from Atlassian Answers will be migrated over to our new community".

However, without checking into the details, I noticed that from my IIRC ~200 answers with some 60+ accepted, only 194 with 49 accepted found their way to this new site.

Can you please clarify which non spam answers have deliberately been left out, if any?

Thanks,
Steffen

6 answers

4 votes

I should have been more specific in the announcement about specifically what we are leaving out. We are splitting the dev community, so dev questions are not in this community. That's what's been left out of the migration. It's anything that was tagged with *-development, mostly. There are a few other tags like 'atlassian-connect' that aren't in.

The dev community is still being built out, but I believe we are thinking that we will not import old content from there. 

Thanks for the explanation Jeremy.

While I completely understand your thinking behind this, I have to say that I strongly disagree with the execution and result of this conceptually reasonable strategy:

Just a random sample across a few of my included/excluded answers, plus a few of fellow community members in my mail archive seems to confirm that the presence or absence of a *-development tag is pretty much arbitrary regarding the classification of the content being primarily developer focused. And I think that's not all that surprising, given tags have been community curated, if at all.

Accordingly, the IMHO highly questionable net result seems to be that a lot of potentially valuable user/admin oriented content is lost, whereas quite some strictly developer oriented content has been migrated.

Given it seems inconceivable to properly classify the questions into either category (except for some fancy machine learning sentiment analysis eventually), is there any chance you might reconsider this and simply migrate the answered yet skipped *-development questions too?

Cheers,
Steffen

Thanks for the explanation Jeremy.

While I completely understand your thinking behind this, I have to say that I strongly disagree with the execution and result of this conceptually reasonable strategy:

Just a random sample across a few of my included/excluded answers, plus a few of fellow community members in my mail archive seems to confirm that the presence or absence of a *-development tag is pretty much arbitrary regarding the classification of the content being primarily developer focused. And I think that's not all that surprising, given tags have been community curated, if at all.

Accordingly, the IMHO highly questionable net result seems to be that a lot of potentially valuable user/admin oriented content is lost, whereas quite some strictly developer oriented content has been migrated.

Given it seems inconceivable to properly classify the questions into either category (except for some fancy machine learning sentiment analysis eventually), is there any chance you might reconsider this and simply migrate the answered yet skipped *-development questions too?

Cheers,
Steffen

<deleted duplicate comment>

Thanks for the info Jeremy. Seems a shame if all those dev questions were lost forever...

Definitely a shame, and beyond that, painful. I was using those dev questions and knowledge to help complete a project due for a client next week and now I need to tell them I'm not able to deliver on time. I can't find the info I need or if I do find it, it takes 5x longer to find.

"we are thinking that we will not import old content from there."

I'm amazed that you are so casually considering consigning the work of thousands of users over many years to the trash.

It's not "old content" - some of it is absolutely current, and of course some of it is old. Unless you intend to delete all "old" (ie all) content every few years, then you and the community need to come up with a process for pruning and keeping things current - just deleting everything now and again is not the right solution.

2 votes
Leslie Lee Atlassian Team Apr 14, 2017

@all - It was the wrong call to remove all development-related tags from the user community. The decision has been reversed and all content is NOW back in the community. 

1 vote
Thomas Schlegel Community Champion Apr 05, 2017

So, what shall we do, if someone asks a question here about writing a script or a user macro? Redirect to the developer community?

Sometimes the line between administration and developing is very small and also, I am not pleased that all these developer-tagged-questions from "Answers" disappeared. 

Hey Thomas,

as scripts and user macro's are part of the regular usages of our tools they are not considered to be developer content.

The Atlassian developer community is specifically focussed on developers who are building on top of our products. 

So questions around how to build an add-on should be sent to the developer community. Everything else can stay in the user community.

1 vote

Hey all,

I've written an article about our decision to separate the community and not to migrate the content.

You can find it here: https://community.atlassian.com/t5/Feedback-Forum-articles/The-Atlassian-Developer-Community/ba-p/459061

 

Strangely, I seem to be unable to post this as a comment to Jeremy's answer (it looks posted, but has vanished on browser refresh), so here it goes as an answer:

----

Thanks for the explanation Jeremy.

While I completely understand your thinking behind this, I have to say that I strongly disagree with the execution and result of this conceptually reasonable strategy:

Just a random sample across a few of my included/excluded answers, plus a few of fellow community members in my mail archive seems to confirm that the presence or absence of a *-development tag is pretty much arbitrary regarding the classification of the content being primarily developer focused. And I think that's not all that surprising, given tags have been community curated, if at all.

Accordingly, the IMHO highly questionable net result seems to be that a lot of potentially valuable user/admin oriented content is lost, whereas quite some strictly developer oriented content has been migrated.

Given it seems inconceivable to properly classify the questions into either category (except for some fancy machine learning sentiment analysis eventually), is there any chance you might reconsider this and simply migrate the answered yet skipped *-development questions too?

Cheers,
Steffen

Steffen, it got caught in the spam quarantine. Now it has appeared here a bunch of times. :/

I see, thanks for the feedback Monique! Pending a solution for How can I delete my own content?, I've stripped the duplicate comment, please feel free to delete it.

As just commented on Why does a posted comment seemingly disappear into thin air without any error message?, "the usability here is obviously not ideal (...), because I had no indication whatsoever that my comment might be in moderation still". So in case the spam trap continues to trigger in certain scenarios even for already established users, I hope this lack of feedback can be remedied down the road ...

For clarity (I hope), I created a seperate question to ask for improvement on the user experience when answers/replies get held up in moderation/spam quarantine: 

Suggestion: Can there be better feedback on responses awaiting moderation?

0 votes

Let me note that the Google index is still full of references to the old Answers site, with highly relevant hits. But, all those links get redirected to the homepage of the new Community site without any explanation. It does not even explain that it is the replacement of the old site... (A more intelligent redirect could be better.)

Although I realize that I can read the old posts using the Cached option of Google, I reckon the majority of the users will not do that.

Result: lots and lots of value and engaged visitors lost!!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Oct 31, 2018 in Feedback & Announcements

November monthly challenge badge is now live!

Ready for another challenge? This month we're challenging you to share your knowledge and answer questions. We're calling it Knowvember! (And by we, I mean me. You can blame me.) To earn this ...

386 views 6 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you