F.A.Qs

Please check that your API configuration has been done properly or check to ensure that you have not unintentionally revoked the API token preventing it from working. In either case, viewing the activity logs will show you a reason why it’s failing.

If all configurations have been set, please ensure that you did not set a date sometime in the future if you require the data immediately.

Please follow this guide to learn How to generate an API token

No, we’ll take care of the configuration and if at any time the configuration is faulty, the app will automatically render a “Fix configurations” button alerting you that something is wrong. Clicking on such a button will find the problem and correct it.

This is because you may have triggered another Jira Cloud backup while the app might be triggering another. In such a situation if multiple backup request is triggered, Jira will require a sort of cooling-off period before another Jira Cloud backup can be initiated. Don’t worry as the app constantly monitors for when the cooling-off period has expired and then triggers the backup

Depending on the situation, you might bump into an error or so, not worry because you can conveniently reach out to our support for help to explain what might have happened. In any situation, checking the activity logs should be your preliminary step towards understanding the problem

The scheduling task creation allows max 50 re-occurring tasks which are shared amongst any user of the app on your site.

Given that the app does not store end-user data, the app does not require data residency. In addition, all data extracted are stored within the same site.

The app servers are located in the EU and the US as AWS infrastructure is utilized.

The app does not store end-user data and moving of data is not done. However, given the functionality of the app, the app does extract Jira issue data by processing the information and discarding the data.

When copying and pasting text from Jira to the app, please ensure that you’re copying text without any newlines as that can cause these types of errors that invalidate a correct JQL. To copy a JQL ensure that the JQL doesn’t have unnecessary newlines or multiple double spacing between each syntax. If in doubt, what you can do is paste the JQL on a text editor and make sure everything is on a straight line then copy and paste those characters into the form fields for the schedule.

Please view the activity log to see why such an error happens. One of the situations, where this issue may arise is if you’re on a free Jira site. The configurations and permissions of Jira become limited and uneditable, making the project where the saved data is visible to all users on your site.

However, you can still create your backup schedule task and perform cloud backup operations.

The app uses your Jira user context to authenticate you into the system. Sometimes, the Jira context might not be readily available for use. That’s why a hard refresh of your browser will typically ensure that the user context is available for the app to detect and utilize for its purposes.

Please when such errors present themselves, follow the on-screen instructions.

If such a problem arises, what you can do is perform a browser refresh by using your browser’s refresh button. Once a refresh is done, you can log in normally.

Ensure that all users of the app who altered the settings configuration for the XML backup option have a valid API configuration set up for their user. This will prevent any errors that could potentially fail the backup task. It would be prudent to always advise all admins to be cautious when altering the XML backup option on the app

Deleting your token will invalidate further use of your token. However, it takes a few minutes before the request is propagated to your Jira site. Typically give between 4 - 7 minutes for the changes to take effect.

Simply navigate to the API configuration page and add your new token then click the submit button to validate the token. If valid, the token status will become active. See How to generate an API token

The extracted files are securely uploaded to your Jira site

The project which is used as storage is specific to Jira administrators

The project is hidden from view and all issues created are hidden with an issue security level.

• On free plans, the permission scheme cannot be edited, therefore the project will be visible to any logged-in user or application user

When the app is uninstalled, the app has a 180-day cycle when it retains your created account details and audit log activities. After 180 days, it will automatically delete all information that was stored during your usage. No end-user data is stored within the app, the only information stored is usage activities. End-user data are always stored within your Jira site

180 days is the maximum our system would be able to retain any activity logs or data once the app is uninstalled. Within, 180 days, you can reinstall the app to reset the clock about account removal.

Since we do not request any information from the app user, we do not send out any notification that your account has been deleted when it does.

Yes, the cloud backup feature is available whether or not you have a valid license for the app. As that feature is a bonus feature, its operation is accessible regardless of an active license.