nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Export / Import data

Stefan

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

Accepted answers

Joe Pitt

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.

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.
Then I suggest you setup Project Roles for the various functions like, tester, QA, Browse Only, etc.
By using project roles, one permission scheme will cover all projects. The project admin controls project role membership
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.

All comments

Joe Pitt

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

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.
Then I suggest you setup Project Roles for the various functions like, tester, QA, Browse Only, etc.
By using project roles, one permission scheme will cover all projects. The project admin controls project role membership
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.

Stefan

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

Stefan

But there is still the question with the import / export

Joe Pitt

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.

Stefan

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

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server