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

Export / Import data

Hi,

we have 2 teams of programmers. One is new to Jira, the other has been working with Jira since about 3 years and is using an older version of Jira.

Now we want to buy a bigger license of Jira and have a Jira server (on premise) with both teams. The existing Jira server is also a local installation and is using "Jira users" (not AD users).

The existing Jira server is only using 1 project. We want to export the old server and import it to the new Jira server. After that we want to change rights, so that only specific users has access to this "old" project. Some of those users should be able to change data, some should only be able to read that data. All users from the "old" server should still be able to change data.

We also want to create more new projects on the new server. Some of those projects should be changeable only be specific users and not be accessible by other users. Some of them should be readable by some users and changeable by others.

 

For setting the user rights we want to follow this thread / explanation:
https://confluence.atlassian.com/cloudkb/how-to-restrict-project-access-for-teams-in-jira-cloud-953142266.html
Did we find the correct one? Since this is for cloud, is it same for local server?

 

Is there also a step-by-step documentation for doing the export / import?

Regards
Stefan

2 answers

1 accepted

0 votes
Answer accepted
Joe Pitt Community Leader Sep 09, 2019

That link gives you the basics. In short terms it is saying:

JIRA works by GRANTING access. You can't restrict access. By default, it grants access to the group used to logon (see Global permissions to see the "can use" groups and admin groups).  This is where users are getting their access.

  1. The FIRST thing you need to do to get control is to remove any groups with logon privileges from the permission scheme unless you absolutely want everyone to have that permission.
  2. Then I suggest you setup Project Roles for the various functions like, tester, QA, Browse Only, etc.
  3. By using project roles, one permission scheme will cover all projects. The project admin controls project role membership
  4. If the project leads want everyone that can logon access to the project they can add the logon group to a project role with the desired permissions.

Thanks! My first test works fine. Should be the way for all options we want to use.

But there is still the question with the import / export :)

Joe Pitt Community Leader Sep 09, 2019

This is what I suggest since you already have JIRA

1. Install the new instance of JIRA on the new server

2. Run the JIRA backup process on the current one

3. Import the backup from step 1 into the new JIRA. It will overwrite the new database with the data from the backup. Now you have a duplicate of you current JIRA on the new server. 

4. Start using the new instance. The easiest way is to change the DNS to point to the new server. 

Ok. But we have different versions of Jira. The "old" one is about 3 years old (or maybe 2 1/2). Can we import the backup of an older version in a newer one? Nothing special to care about?

Joe Pitt Community Leader Sep 10, 2019

Going forward isn't a problem. However, you may have to do it in steps. Look at the upgrade notes in the new version. It will tell you what versions you can directly import a backup from.  If it doesn't support you version look for the oldest one and see if that one supports importing from you current version. You may need to install a 'bridge' system to install your backup into and then back that version up and import it into the current version. You won't need to connect to your normal database or network. Just use the one that comes with the trial version. You can probably do it on a newer laptop. Make sure to install any plugins you're using into the bridge system with the plugin version for the bridge version.  This is why you shouldn't let your tools get too old

Like Stefan likes this

Thanks for your support!

Joe Pitt Community Leader Sep 10, 2019

Good luck

I found the upgrade notes for 8.4.0 here:

https://confluence.atlassian.com/jirasoftware/jira-software-8-4-x-upgrade-notes-975017731.html

But I can't see any hint regarding the Jira version where I can restore a backup from? The old version is that we have is Jira 6.4.10 and Jira Agile 6.7.11

Joe Pitt Community Leader Sep 10, 2019

I looked at the upgrade technical notes at https://confluence.atlassian.com/adminjiraserver/upgrade-matrix-966063322.html#Upgradematrix-notes and they only go back to 7.4. I would contact Atlassian support to see what they recommend. It looks like you'll need at least one bridge version to upgrade. 

Like Stefan likes this

ok. Thanks again for your help!

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

231 views 1 2
Join discussion

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