DB migration to migrate 'violations'/'reviews' tables to 'issues' table

Migration process :

• Truncate the table ISSUES and ISSUE_CHANGES if exist (reentrancy)
• Remove duplicated rows in the REVIEWS table (see SONAR-3745) -> same RULE_FAILRE_PERMANENT_ID
• Add and feed the ACTION_PLANS.KEE column
• For each rule failure load the relating data from RULE_FAILURES, REVIEWS, REVIEW_COMMENTS, ACTION_PLANS_REVIEWS tables and insert some new rows in the ISSUES and ISSUE_CHANGES columns
  • For any violation
    • ISSUES.ISSUE_CREATION_DATE=ISSUES.CREATED_AT=RULE_FAILURES.CREATED_AT
    • ISSUES.UPDATED_AT=NOW
    • ISSUES.RULE_ID=RULE_FAILURES.RULE_ID
    • ISSUES.MESSAGE=RULE_FAILURES.MESSAGE
    • ISSUES.LINE=RULE_FAILURES.LINE
    • ISSUES.EFFORT_TO_FIX=RULE_FAILURE.COST
    • ISSUES.CHECKSUM=RULE_FAILURE.CHECKSUM
  • For any violation WITHOUT review :
    • ISSUES.STATUS=OPEN
    • ISSUES.ISSUE_UPDATE_DATE=RULE_FAILURES.CREATED_AT
    • ISSUES.SEVERITY=conversion of RULE_FAILURES.FAILURE_LEVEL
    • ISSUES.MANUAL_SEVERITY=false
  • For any violation WITH review :
    • ISSUES.ISSUE_UPDATE_DATE=REVIEWS.UPDATED_AT
    • ISSUES.STATUS=REVIEWS.STATUS
    • ISSUES.RESOLUTION=REVIEWS.RESOLUTION
    • ISSUES.REPORTER=REVIEWS.USER_ID
    • ISSUES.ASSIGNEE=REVIEWS.ASSIGNEE_ID
    • ISSUES.SEVERITY=REVIEWS.SEVERITY
    • ISSUES.MANUAL_SEVERITY=REVIEWS.MANUAL_SEVERITY
  • Quid ISSUES.AUTHOR_LOGIN (see RULE_FAILURES.PERSON_ID) ?
• Drop the RULE_FAILURES, REVIEWS, REVIEW_COMMENTS, ACTION_PLANS_REVIEWS tables