Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the migration path for existing users? #34

Closed
bkeepers opened this issue Jun 27, 2018 · 4 comments
Closed

What is the migration path for existing users? #34

bkeepers opened this issue Jun 27, 2018 · 4 comments

Comments

@bkeepers
Copy link
Contributor

From the scope doc:

It is unknown what the migration path is for existing users.

@andymckay andymckay changed the title What is the migration path for exiting users? What is the migration path for existing users? Jul 3, 2018
@andymckay andymckay added this to the Initial release milestone Jul 3, 2018
@jmilas
Copy link
Contributor

jmilas commented Jul 9, 2018

As an update here, we've been chatting with the folks from Atlasssian about this, but it's still unclear what this migration path will be.

Given the best information about the current DVCS usage lives with Jira, we've requested that they provide some form of in-product or email prompt to users to migrate to the new integration, but we're waiting to hear back about what specifically they're able to provide and what work (if any) we may need to do to support it.

@jmilas
Copy link
Contributor

jmilas commented Aug 8, 2018

Adding some details here now that we know more. The flow will look like:

  1. Existing users will receive an email and/or in-product prompt from Jira to install the new integration.
  2. After installation is complete, the integration should sync historical data (tracked separately in Syncing data on initial setup #35)
  3. Once this sync is complete, the integration will call an endpoint (to be provided by Atlassian 🔜, but I'm told will just be an empty POST request) to inform them that they can disable the existing DVCS connector.

cc: @andymckay, @tcbyrd, @bkeepers to continue the conversation about this. I believe the remaining work to complete this ticket just involves incorporating the forthcoming endpoint from step 3.

@andymckay
Copy link
Contributor

Once this sync is complete, the integration will call an endpoint

Does that imply some sort of time limit or expectation around syncing? Based on the comments in #35 that might take quite a while (if it possible for everything)

@jmilas
Copy link
Contributor

jmilas commented Aug 9, 2018

Does that imply some sort of time limit or expectation around syncing?

Good question. Do we have a rough estimate for how long "a while" would be? Hours, Days? If we expect the sync to take more than a few hours, I think we can propose that we call the endpoint once install is complete but before the sync is complete.

@tcbyrd tcbyrd closed this as completed Sep 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants