I'm trying to get my development environment system configuration to be the same as what is in production.
First let me say that "NO" I cannot get a copy of the production system brought down to my dev environment. The process will take 3 months to get approval, and that is best case scenario.
So, I'm trying to get things to match up Apples to Apples not Apples to apple if you know what I mean.
I need to create new workflows and schemes that have the same configuration and names as what is in production. I thought I could just go into the database and rename the current ones to prefix them with Wrong and the new ones with the correct names.
For example the current 'My Project Workflow' has the wrong values and I cannot modify them. So, I created a new workflow 'New My Project Workflow' with the correct values.
I go into the database and alter
'My Project Workflow' – > 'Wrong My Project Workflow'
'New My Project Workflow' – . 'My Project Workflow'
When I try to associate any organization with the workflow it then throws errors in the log stating
...WorkflowException: Could not find workflow associated with project 'OrgName', issuetype 8
Is there an easy way to rename this?
Or do I have to dis-associate every organization from the workflow
then delete that workflow
then recreate the workflow
then reassociate the organizations to the new workflow?
I have about 80 organizations and this is taking forever to manage.
Try a plug in for JIRA called Configuration Manager. It takes an XML snapshot of the entire project or system and can be deployed on another system via the same add-on. It is great. It does not grab content (issues). Those can easily be CSV imported though.
You should not have changed anything in the database for a start - you've messed up the setup and it's probably going to be easier to throw everything away and start again. You certainly need to roll back to what you had before messing with the database at the very least.
You've got three basic options here
You can solve this issue easily with Configuration Manager for JIRA. You can create a system snapshot from the production server and deploy it on the dev using "Restore" mode which was created exactly for the use case that you are describing. If you need any assistance or have some questions or comments don't hesitate to drop us an email at firstname.lastname@example.org
George, Botron Software
I was afraid these were going to be my answers. The best one I can use is 'Copy the setup by hand' only issue is that I don't understand exactly how all of the pieces tie together. Downloading any software in my work-space is prohibited and bringing in and software is prohibited.
Thank you both for the input.
At least I have an interview this afternoon and plan on taking whatever to get out from under this horrible project.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs