Data truncation error when entered a long URL custom field which breaks the Move Issue process

Here are the steps to reproduce this bug:

1. Create 2 new projects (Project A & Project B)
2. Create a URL custom field type and set it applicable only to Project B
3. Create a new issue in Project A (e.g: PRA-1)
4. Click on 'Move this issue' operation
5. Select on Project B and any issue types
6. Fill in a long URL that exceeds its max char length 255 - http://test.website.com/?test1=1&test2=12312401275019254uoiafjp192084709847019850129835laiwuhfiawuefhlawioefhlawiufhawleifuhawilehfalwiefhawlifuhalwiehfalwiehflaiwuhflaiwuhfaliwhflaiwefhlaiwuhflaiwefalwiefhalwiefuhawliefuhawliehfalwihfawlihfalwiefuhalwiefhlawiehflaiwefhaliwefhalwiefuhlawieuhflaiwehflawiuefhalwiehfalwiehfalwiehfalwiehfalwiehflaiwefhlawiefhliawehflawiehfalwiehflawiehfa
7. Click on 'Move' button in Step 4 of 4
8. You will hit into the following error:

   com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:CustomFieldValue][id,10001][stringvalue,http://test.website.com/?test1=1&test2=12312401275019254uoiafjp192084709847019850129835laiwuhfiawuefhlawioefhlawiufhawleifuhawilehfalwiefhawlifuhalwiehfalwiehflaiwuhflaiwuhfaliwhflaiwefhlaiwuhflaiwefalwiefhalwiefuhawliefuhawliehfalwihfawlihfalwiefuhalwiefhlawiehflaiwefhaliwefhalwiefuhlawieuhflaiwehflawiuefhalwiehfalwiehfalwiehfalwiehfalwiehflaiwefhlawiefhliawehflawiehfalwiehflawiehfa][issue,10001][parentkey,null][customfield,10000] (SQL Exception while executing the following:INSERT INTO customfieldvalue (ID, ISSUE, CUSTOMFIELD, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation: Data too long for column 'STRINGVALUE' at row 1))
   

9. Go back to the Issue navigator and do a search for Project A
10. Click on PRA-1 issue key and you will be seeing "ISSUE DOES NOT EXIST":

    Error
    
    The issue you are trying to view does not exist. 
    

11. Try to search for Project B and you will find no issues were shown
12. Looking inside the database and doing a select query for project A, the issue is not there anymore:

    select * from jiraissue where pkey='PRA-1';
    

13. But, doing a select query for project B, the issue will be shown:

    select * from jiraissue where pkey='PRB-1';
    

Well, the problem would be solved after running a full re-index via Administration -> System -> Indexing but this is definitely a bug.

The reason is because since the move process have been interrupted with the "Data truncation" error, the issue should not be moved to another project and thus, delete off the old issue.