Hi, My company will be migrating from Server to Cloud in q1 next year. I was hoping you could help with a couple questions.
1. Is there a best practice step by step guide for the move?
2. Is there test automation for workflows on the migration to cloud? Automated scripts that will help test functionality to assure the workflow is working as should. Or would a manual test of every workflow be required.
3. Is there a way to use a separate storage location for attachments on tickets like another bucket for attachments. This would be because of PHI & PII coming across in the migration that we can't have happen.
Thank you for any help with these questions. And I hope they make a little sense on what I am asking. :)
Hi Dave,
as for topic 2): no, there is no automated solution. In that sense it would process your issues through a workflow - this is something some customers would not accept.
You would have to do that on your own, if you explicitly want to test-automate it you could try something via API.
As migration (in best case) is a one-shot I am in doubt if this would be worth the effort. It might be quicker to process a test issue in each project "one-off" through the corresponding workflow.
as for topic 3): attachments will be along with issue data in the Cloud, after migration. There is no option to have them stored elsewhere. The storage location is defined by Atlassian and cannot be changed.
You have some options to finetune them but no option to store them somewhere else:
https://support.atlassian.com/jira-cloud-administration/docs/configure-file-attachments/
Cheers,
Daniel
Hi @Dave Hattig,
Find the cloud migration guide right here.
If you have decided to migrate during Q1 next year, start by going through the guide. Next, create a migration ticket with Migration support. They'll be happy to help you with answers to all questions you may have.
And most of all: take your time to thoroughly prepare. Depending on the complexity of your Server instance and requirements you may have, it may well take a couple of months before you're all done in production. Don't hesitate to let a solutions partner support you in the process if it seems there's a couple of tricky bits in the migration. If all goes well, you're gonna do this once - it's always good to be guided by folks who already have a couple of these under their belts.
And as always, every journey starts with taking the first step! So happy reading - I wish you a very smooth migration!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dave,
On your point above "Is there a way to use a separate storage location for attachments on tickets like another bucket for attachments. This would be because of PHI & PII coming across in the migration that we can't have happen"
Could you give me more information on this? As Daniel points out above the attachments will live next to the issue data on Cloud. Were you looking for something like a 'bring your own storage provider'? Are you hosting all attachments somewhere like Box or Dropbox already?
Keen to learn more about your requirements.
Thanks
Owen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Owen,
We don't host our attachments anywhere other than attached to the issues. We are still in our planning/research phase, but we need to figure a way to scrub all PHI and PII from issues. And we have most of it figured out except for attachments that may store any health info.
Thanks
-Dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.