Stop Awnaba project configurator backup


Does anybody know how to stop JIRA backup after successfully uploaded project configuration file by

project configurator  add-on?

Thank you



3 answers

Hi Fleming, Could you clarify the question? Do you mean the JIRA XML backup? In principle, that has nothing to do with Project Configurator add-on. Both are completely independent pieces of functionality. Maybe, if you explain the steps you have taken, the result you get and the result you expected, this could be sorted out. You are welcome!

Hello, Thanks for your reply! Actually, we are using Project Configurator to import project from developing jira instance. For sure, it must be very careful to modify the exported configure xml file then upload it by Project Configurator import. After each import, we found there is a xml backup in jira home/export. So, I wonder maybe Project Configurator do trigger jira backup after successfully upload. Our Project Configurator vesion is 1.6 , JIRA 5.2.11 BTW, we have several Project Configurator unlimited license. Want to know how to get the awnaba support for Project Configurator. Any suggestion would be appreciated!

Starting from the end, you can get support from Awnaba Software for Project Configurator by any of the means outlined at the "Support" tab in the plugin page at the Marketplace. Look at the "Resources" section on the right side. We highly recommend using our issue tracker at above the other support channels. As a support tool, JIRA is far more powerful than Atlassian Answers!

We have reproduced the problem you describe in your question. There is an automated backup service that is set to run in JIRA every 12 hours (as a default) as explained in this page. It seems that running an import with Project Configurator triggers that backup service, even if it is earlier than 12 hours since the last backup. Currently, the workaround available would be to remove that service before running the import.

AFAIK there is no way to stop the backup once it is running.


Hi Fleming, Just a quick update on this answer. Further tests have shown that this problem does not always happen after each configuration import. So the issue reproducibility is not as clear-cut as we would like. We think this might be related to issue, whose fix is planned for the next plugin version (1.8). Please stay tuned to the news...

Hi Fleming, Have you upgraded to version 1.8 (released at the end of October)? In that case, has this problem stopped? Regards!

Hi, Actually it's a long way for us to upgrade jira from 5.2.11 to 6.X or 7.X. Thank you for workaround suggestion. We are using your product for cloning jira project within jira stance and deploying project which is in developing jira instance. Of course, we did it on the base of your exported XML. That bug is not happened all the time. I mean from dev to uat is ok, but uat to production. If we've done the upgrade job, we'll be still use your product then may report you the bug is disapper or not. Anyway, thank you for your great support.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 13, 2019 in Marketplace Apps

Marketplace Spotlight: Marketing apps for Confluence to keep your teams working on the same page


271 views 0 7
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you