Create a Jira multi select field which loads a list of options from REST API dynamically

[Andrian Fernandopulle]

Hello All,

I have 4 different Jira instances. I use one Jira instance to manage project changes. So I need a way to get all projects names from 3 different instances into one.

Ex scenario: User selects the "Instance A" from the Jira Instance field & I want to make a REST call/mysql query to that instance and get a list of projects & display that in the Jira Project/s field which is a multi select field. 

Jira Instance: 

    Instance A

    Instance B

    Instance C

Jira Project/s:

    Project AA

    Project AB

    Project AC

I tried using nfeed. With that I need to have 4 different fields for each instance because one REST call per instance can only be mapped to one field. I cannot associate one field with multiple data sources. 

Anyone done something similar ? Any ideas on how to get all these data into one field ?

Any thoughts & advise appreciated.

NOTE

As of now we are using a text field to capture this project info but we need a dropdown field to capture these & report on them. We have so many projects in each instance and we do not want to create a custom field and manually manage them.

Thanks in advance.

[Nic Brough -Adaptavist-]

Er, the documentation absolutely does cover moving from one server to another, upgrading and changing databases amongst other things. I don't think you've bothered to look for it frankly. Try any search engine for "jira upgrade" and you'll find hundreds of links to the Atlassian documentation.

Anyway. The order is up to you. You could upgrade your current system in place, then move it. Or move it, then upgrade it. Or do both at the same time.

I'd tend to do move then upgrade myself, with a view to doing both at the same time - the reason is that if you don't touch the old original server, you've got a fail-back if your live implementation goes wrong. It all depends on how your testing goes as to whether you think it's possible/safe to do it all in one go.

[vidhi goyal]

I make it simple for me. i just want to move JIRA from one server to another. I don't want any upgrade. What is the steps for it.

[Nic Brough -Adaptavist-]

Follow the docs for migration. The short version is create a new Jira install on the new server, copy the data from the home directory, point it at the database and start it up.

[vidhi goyal]

Actually we are cloning the server. So do I need to install Jira again or change in the configuration file fro server and BD is enough to run the JIRA

[Nic Brough -Adaptavist-]

No, you probably won't need to install anything if you are cloning. I assume your home directory for Jira is included in the clone.

[vidhi goyal]

yeah it will be there but I want to know what all configuration I need to change I did not get any document.

[Nic Brough -Adaptavist-]

The first hit on google is "Migrating Jira to another server". I'm not sure why you can't find that.

[vidhi goyal]

I saw the doc on Migrating jira to another server but there they are again installing it new server. My question is I have a cloned server. In that how will i configure JIRA wrt new database and new server details. I can change database using jira config wizard.what about new server details. Is there any specific steps for it.

[Nic Brough -Adaptavist-]

The advantage of cloning a server is that you don't have to do most of the configuration in the "migration" document. But you DO need to go over the document to check what you need to change in your specific environment. Although "nothing to change" is a perfectly valid answer there.

If you're moving the database as well, then yes, you'll need to change the connection to the database in the new system, but you shouldn't need to change anything else. All the "specific steps" you're asking for are in the migration document, I'm really not sure what's missing here.