Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why is our Stride data export incomplete? Edited

We're in the midst of migrating from Stride and HipChat to Slack. I referred to this page for instructions:

https://www.atlassian.com/partnerships/slack/migration#stride

Both tools worked smoothly. However, once the import was done, I only have 1 room (should be ~10), and virtually no message history. The room has no messages, and neither do most chats; a single 1:1 chat between me and a coworker has a handful, including some (randomly) in July 2018. It doesn't look like the Slack import is to blame: it shows only 1 room and 10 total messages were found in the export.

And that makes sense: the Stride export happened suspiciously fast, and if I download the file, it's only 5KB. (FYI, I said "yes" to include public rooms, private rooms, and 1:1 messages in the export config.)

So... why might that happen? I'm a site admin for our Atlassian account; just in case, I had another site admin create an export, but with the same results.  Is this a known issue? Are there any workarounds or other approaches to try?

Thanks!
Jeremy

1 answer

1 accepted

0 votes
Answer accepted
MarcusEllis Atlassian Team Nov 19, 2018

Hey Jeremy,

Sorry you're experiencing this issue. I'm a member of the team that worked on the Stride Exporter. I'm not sure what's going wrong, but I expect my team will be able to resolve the issue rather quickly once we can get a bit of information from you.

Can you provide the job ID for the export that is not working as expected? It should look something like this: "b9c6eb98-ec65-11e8-8eb2-f2801f1b9fd1"

Regards,
Marcus Ellis

Hey Marcus,

Thanks for the response. And sure - I debated including it in my initial post. Here are the two we've run, in order:

638f1fea-e4a8-4731-a5a1-30498226ffe6

b61bc8fd-2df7-4e4a-b187-9a76e569c221

 

-Jeremy

Jeremy,

Thanks for sending those along. They're random IDs and are only used for that single export job, so they're safe to share here. They have no special meaning.

We're looking into it now. But just to confirm, you've selected all 3 checkboxes and aren't specifying a date range, correct?

And if you could provide a rough estimate for how many rooms and messages you would expect to be in the export, that would helpful too.

Thanks,
Marcus

Marcus,

Correct. I just ran a third one with the same general results (i.e. a 5KB file) - I'm attaching a screenshot of the settings I used.

Hard to say on the number of messages, but the project in question goes back over a year with probably some dozens of messages - automated and personal - per weekday (and those are just the public ones). So probably 5-figures or so? Looks like we have 17 rooms.

And understood on the ids. I realize they're randomized and non-sequential, but if there were a security flaw on Atlassian's side that could be exploited if one knows the direct id of something like an export job, I just wanted to minimize the odds of a breach. However, even in that case, those particular exports have so little data that not much is at risk. :P

Thanks again for looking into it!

Jeremy

2018-11-20_11-26-02.png

MarcusEllis Atlassian Team Nov 20, 2018

Hey Jeremy,

We've done some digging and from what we can see on our end, that export looks to be correct. We're not seeing any errors or warnings in our logs, but we're also not seeing additional rooms, which is a bit confusing.

I think the best thing to do at this point is to open a support ticket at https://support.atlassian.com/contact/. This we can communicate more privately and dig a little deeper into this specific issue.

Thanks,
Marcus

Like Jeremy Thompson likes this

Hey Marcus,

Your last post made me question my assumptions; digging further, I see that the problem is account confusion. Most that we do (Jira, BB, Confluence, Stride) is under one account, but the Stride I want to export lives under a second that, AFAIK, only hosts Stride. The one in our main account contains little and matches my export.

Sorry to send you running down a false path. I'm working on getting access to the secondary account now, which I'm pretty confident will work fine. Thanks again for your help!

-Jeremy

MarcusEllis Atlassian Team Nov 26, 2018

Jeremy,

Glad to hear you've figured out what the problem was. I was curious if something like that might be the case.

Please do let us know if you run into any other issues.

Regards,
Marcus

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Stride

Stride and Hipchat Cloud have reached End of Life (updated)

All good things come to an end - thanks to all our customers and partners who have been along the Hipchat and Stride journey with us.  As of Feb 15th 2019, Hipchat Cloud and Stride have reached ...

2,422,244 views 26 26
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you