Jira MySQL question

[Gabriel Meyer]

The MySQL db folder was moved while the service was live, and it ran over the weekend.  The error was caught the following Monday and the db folder moved back.  

It appears that when some users are trying to work, they experience the following error:

org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:ChangeItem][newvalue,3][field,status][oldstring,Open][newstring,In Progress][id,103832][fieldtype,jira][oldvalue,1][group,80957] (SQL Exception while executing the following:INSERT INTO changeitem (ID, groupid, FIELDTYPE, FIELD, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING) VALUES (?, ?, ?, ?, ?, ?, ?, ?) (Duplicate entry '103832' for key 'PRIMARY')) It seems that you have tried to perform an illegal workflow operation. If you think you shouldn't get this message, please contact your Jira administrators.

Is there a way to repair the items that were added while the database was not functional, or is the best option to restore from the point in time from right before this all happened?  What should be exported in order to get the data back?  Is this even possible?  For the restore, what data should be restored?  

I appreciate any assistance we can get with this.

[Moses Thomas]

@Pablo Fernandezif you  want to  change these issue types to  subtask  you  just  bulk move them  i.e you  can move any  issuetype  to  subtask . If you  don't  want  any  other issue type to  be in the issue type scheme then remove them  and leave  only  subtask but  when  you  BULK  move them  to  subtask,   they will  have the issue type subtask.

[Moses Thomas]

@Pablo FernandezIf you have subtask  issue type in your issue type scheme/add subtask issue type,   enter  the project   and you  can perform  bulk  operation around  the search  box for issues look for tools > bulkchange  and you can  move all  tickets to  subtask.

Best!

[Pablo Fernandez]

Hi @Moses Thomas, thanks for answer. If i understood correctly your comment, you are talking about moving existing tickets from task to sub-task, this is not the case.

Standing in the issue administrator, editing the issues type scheme, there are existing types of issues that i need to convert into sub-task, so in the future it wouldn't be necessary to move every ticket to a sub-task.

For example: in my scheme a Change Request issue is a task, but i need it to be sub-task directly in the scheme.

I need to be able to edit those existing issue types. I'm asking if that possible or if the solution is to create a custom issue type again.

Thanks you for your help, please let me know if i misunderstood your previous comment.