My company has been using a single JIRA Agile account for a number of project over two departments. Due to a fast growth we would now function much better if we could split the existing account in two, one per department, each with its own projects, while keeping all the issues, schemas, workflow, etc.
Is it possible?
Hi Nic, thanks for your answer. I have a couple of follow-up questions:
We're about to buy a new JIRA instance and start the migration, but I have a follow up question:
Our current JIRA is 100 Users, for the new one we need a 25 users instance. What happens with the import process? Is it going to ask to deactivate users during importing? Should we get a bigger instance, then deactivate users and scale it back? How easy is it to scale back from 100 to 25, and does that cost anything?
On Cloud, I'm not actually sure.
On Server, the import would carry the 100 user licence over, and then go read-only after you apply the 25 user licence until you got the numbers down. On Cloud, the licence might not be transferred, so I'd expect read-only until you drop the numbers.
But, Cloud billing is supposed to be "we charge you for the users you had that month", so it may import 100, you get charged for 100 for a month, and then it drops to 25 after you reduce the numbers down
We're in the middle of testing the migration and clean-up. I have a follow-up question: it doesn't look like Confluence has been exported as part of the process. Does that need a separate, dedicate migration? Is that the same workflow?
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG