How can I migrate and merge a set of jira projects into a single project on a new server?
We have a set of Jira projects on a server, that we need to move to a new server. At the same time we wish to merge those projects into a single project.
How can this be done, preserving workflows, columns, permissions, filters, components, etc.?
I see how to migrate an entire server, one for one, but I am not seeing a way to merge and migrate select project instances. Also, the target server is already hosting many other projects, which we do not want to blow away
jira
add a comment |
We have a set of Jira projects on a server, that we need to move to a new server. At the same time we wish to merge those projects into a single project.
How can this be done, preserving workflows, columns, permissions, filters, components, etc.?
I see how to migrate an entire server, one for one, but I am not seeing a way to merge and migrate select project instances. Also, the target server is already hosting many other projects, which we do not want to blow away
jira
add a comment |
We have a set of Jira projects on a server, that we need to move to a new server. At the same time we wish to merge those projects into a single project.
How can this be done, preserving workflows, columns, permissions, filters, components, etc.?
I see how to migrate an entire server, one for one, but I am not seeing a way to merge and migrate select project instances. Also, the target server is already hosting many other projects, which we do not want to blow away
jira
We have a set of Jira projects on a server, that we need to move to a new server. At the same time we wish to merge those projects into a single project.
How can this be done, preserving workflows, columns, permissions, filters, components, etc.?
I see how to migrate an entire server, one for one, but I am not seeing a way to merge and migrate select project instances. Also, the target server is already hosting many other projects, which we do not want to blow away
jira
jira
edited Nov 27 '18 at 22:14
Victor Grazi
asked Nov 27 '18 at 21:51
Victor GraziVictor Grazi
5,542124273
5,542124273
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Unfortunately, there is no out of the box solution I'm aware of. In my opinion you have two options:
a) If this is a one-time task: Merge your instances into one without merging projects together. Then, merge your projects e.g. by bulk moving issues into one specific project. If you already have a server hosting many projects, then you could also setup a separate server where you do the migration on, move everything into one project and later move this single project back (if necessary).
b) If this migration should be a continuous task and your highest priority is the migration of issue data: there are Atlassian marketplace apps which can synchronize issues between two different projects, so that you have the same issue data in two projects. You could use one of these apps and setup synchronizations between projects in the way like B to A, C to A, D to A, ... They will then do the job for you to "migrate" the issue data into one project. Please consider that such apps might not migrate EVERY data you want, e.g. you could lose certain settings, permissions or filters, because these apps are focused on actual issue data. Disclaimer: I'm a developer for one of these sync apps.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53508742%2fhow-can-i-migrate-and-merge-a-set-of-jira-projects-into-a-single-project-on-a-ne%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Unfortunately, there is no out of the box solution I'm aware of. In my opinion you have two options:
a) If this is a one-time task: Merge your instances into one without merging projects together. Then, merge your projects e.g. by bulk moving issues into one specific project. If you already have a server hosting many projects, then you could also setup a separate server where you do the migration on, move everything into one project and later move this single project back (if necessary).
b) If this migration should be a continuous task and your highest priority is the migration of issue data: there are Atlassian marketplace apps which can synchronize issues between two different projects, so that you have the same issue data in two projects. You could use one of these apps and setup synchronizations between projects in the way like B to A, C to A, D to A, ... They will then do the job for you to "migrate" the issue data into one project. Please consider that such apps might not migrate EVERY data you want, e.g. you could lose certain settings, permissions or filters, because these apps are focused on actual issue data. Disclaimer: I'm a developer for one of these sync apps.
add a comment |
Unfortunately, there is no out of the box solution I'm aware of. In my opinion you have two options:
a) If this is a one-time task: Merge your instances into one without merging projects together. Then, merge your projects e.g. by bulk moving issues into one specific project. If you already have a server hosting many projects, then you could also setup a separate server where you do the migration on, move everything into one project and later move this single project back (if necessary).
b) If this migration should be a continuous task and your highest priority is the migration of issue data: there are Atlassian marketplace apps which can synchronize issues between two different projects, so that you have the same issue data in two projects. You could use one of these apps and setup synchronizations between projects in the way like B to A, C to A, D to A, ... They will then do the job for you to "migrate" the issue data into one project. Please consider that such apps might not migrate EVERY data you want, e.g. you could lose certain settings, permissions or filters, because these apps are focused on actual issue data. Disclaimer: I'm a developer for one of these sync apps.
add a comment |
Unfortunately, there is no out of the box solution I'm aware of. In my opinion you have two options:
a) If this is a one-time task: Merge your instances into one without merging projects together. Then, merge your projects e.g. by bulk moving issues into one specific project. If you already have a server hosting many projects, then you could also setup a separate server where you do the migration on, move everything into one project and later move this single project back (if necessary).
b) If this migration should be a continuous task and your highest priority is the migration of issue data: there are Atlassian marketplace apps which can synchronize issues between two different projects, so that you have the same issue data in two projects. You could use one of these apps and setup synchronizations between projects in the way like B to A, C to A, D to A, ... They will then do the job for you to "migrate" the issue data into one project. Please consider that such apps might not migrate EVERY data you want, e.g. you could lose certain settings, permissions or filters, because these apps are focused on actual issue data. Disclaimer: I'm a developer for one of these sync apps.
Unfortunately, there is no out of the box solution I'm aware of. In my opinion you have two options:
a) If this is a one-time task: Merge your instances into one without merging projects together. Then, merge your projects e.g. by bulk moving issues into one specific project. If you already have a server hosting many projects, then you could also setup a separate server where you do the migration on, move everything into one project and later move this single project back (if necessary).
b) If this migration should be a continuous task and your highest priority is the migration of issue data: there are Atlassian marketplace apps which can synchronize issues between two different projects, so that you have the same issue data in two projects. You could use one of these apps and setup synchronizations between projects in the way like B to A, C to A, D to A, ... They will then do the job for you to "migrate" the issue data into one project. Please consider that such apps might not migrate EVERY data you want, e.g. you could lose certain settings, permissions or filters, because these apps are focused on actual issue data. Disclaimer: I'm a developer for one of these sync apps.
answered Nov 29 '18 at 7:52
s.hesses.hesse
44125
44125
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53508742%2fhow-can-i-migrate-and-merge-a-set-of-jira-projects-into-a-single-project-on-a-ne%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown