Integrated Repo Data Loss

[Audrey Gehring]

We added about 350 repos to the Jigit Config Page in Jira in late December (indexing all repos). As of 1/25, everything looked normal. On 1/26, we noticed that almost all of the repos were gone from config page, except for a small batch that had been added about a week prior to the 26th. We have investigated logging to try to figure out what happened.

Can you think of anything in the source code that would cause this loss?

In addition, do you have plans to add more INFO logging logic so that we can see clearly in logging when things are edited/added/deleted?

[Dmitrii Apanasevich]

Hi Audrey,

The only way to remove a repo is to click "Remove" button.

Hope, it's an issue of displaying repos at the config page.

Settings are stored in JIRA database in JSON format. Let's check them with a simple SQL query:

select propertyvalue
from propertytext join propertyentry on propertyentry.id = propertytext.id
where propertyentry.entity_name = 'com.apanasevich.jira-jigit-plugin'

Don't show me a result, just check how many repositories are there. If it's difficult to you to identify this, replace secure information (URLs and tokens) and attach a result here as file.

Feel free to ask questions.

[Audrey Gehring]

Hello Dmitrii,

Thank you for your quick response.

Running that query returned 69 repos (which is the same as the current count on the config page in Jira). That is what we expect as of adding back some of the original 350.

So as far as you know, nothing should cause that field to remove data except by hitting the button?

Is there anything else you would recommend as far as troubleshooting? We have a backup with all of the lost data, but we are wary to replace the data in case this happens again.

Best, Audrey

[Dmitrii Apanasevich]

So as far as you know, nothing should cause that field to remove data except by hitting the button?

The only exception is a bug, because 'remove' method is called only in controller of "Remove" button.

Is there anything else you would recommend as far as troubleshooting? We have a backup with all of the lost data, but we are wary to replace the data in case this happens again.

Well, you can restore a backup as a new database and update only propertytext.propertyvalue by adding missing repos. Let me know if you need help with SQL update query for this purpose.

I'll add INFO logging on add\delete\edit actions, please create an issue for this.

[Audrey Gehring]

Dmitrii,

Thank you. I have added the INFO logging issue. I look forward to that feature. That way we'll have something to refer to if this happens again.

I will work with my team to restore, but thank you for your help!

Audrey

[Dmitrii Apanasevich]

Ok. I'll close this issue, but it still will be available for comments.

Keep me up to date on news if you will find something important.