[FOLIO-1998] Duplicate Issue Keys in UXPROD JIRA Project Created: 02/May/19  Updated: 03/Jun/20  Resolved: 02/May/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P1
Reporter: Holly Mistlebauer Assignee: Holly Mistlebauer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Text File CSV-configuration-201905011709.txt     JPEG File ErrorMessageOnScreen-Final.JPG     Text File Finallog.txt     Microsoft Word Import Rankings - Final.csv     Microsoft Word Issues2Fix.xlsx     PDF File JIRADuplicateIssuesWithErrorMessages.pdf    
Issue links:
Relates
relates to FOLIO-1987 Import Gap Analysis/Feature Ranking d... Closed
Sprint:

 Description   

The UXPROD JIRA project currently has 2 issues each with the following JIRA issue keys:

If you attempt to search for one of these Issue Keys, or use a direct URL such as https://folio-org.atlassian.net/browse/UXPROD-37, you will get a 500 error. The best way to find one of these issues is to search for the Summary. The attached Issues2Fix.xlsx spreadsheet provides the Summaries. After you search for a Summary and attempt to open one of these issues, you will receive this error: "UXPROD-XX can not be opened. The issue may have been deleted or you might not have permission to see the issue." (The attached file JIRADuplicateIssuesWithErrorMessages.pdf shows all of the issues as they exist in JIRA, along with the error message.) The message is a bit misleading. The trouble is that there are two issues with the same Issue Key and JIRA doesn't know what to do about that. So how did this happen? Let me explain...

Yesterday I did a batch import of the new Gap Analysis/Feature Prioritization rankings for 11 of our community members. I imported only the rank fields and only into the UXPROD project. Attached file Import Rankings - Final.csv is what I imported and CSV-configuration-201905011709.txt is the configuration (i.e. mapping) file I used. The import appeared to finish processing successfully, then a red box appeared with this message: "Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state." (I have also attached the screen print as file ErrorMessageOnScreen-Final.JPG)

I checked the log (attached file Finallog.txt) and figured out that the problem occurred at issue UXPROD-37 Closed . I went to look at issue UXPROD-37 Closed and received the error message that it could not be opened. I then tried UXPROD-38 Open and could not open it either. I then went ahead and successfully imported the remaining updates except for UXPROD-37 Closed and UXPROD-38 Open .

Because of this error, I decided to carefully check out all of the updates to make sure they were made correctly. This is how I came across the problem with 5 of the issues being duplicates. Here is what I believe caused the problem, although I have no idea why JIRA did what it did:
1) I created the Gap Analysis spreadsheet during the first week of March.
2) At some point later in March or in April, five UXPROD issues related to the Data Warehouse were moved from the UXPROD project to LDP.
3) When I imported the Gap Analysis spreadsheet into JIRA, the Issue Keys for the five moved issues were still in the spreadsheet. JIRA pulled the issues from LDP back into UXPROD and then assigned them Issue Keys that were already being used by other issues. I would have expected JIRA to give an error. Given JIRA knows the old UXPROD Issue Keys I am not sure why JIRA didn't just assign them back.
4) When JIRA encountered UXPROD-37 Closed in the import file, it didn't know what to do because there were two records in the database with that Issue Key.

So now we have some cleanup to do. I would like to leave the issues that originally had the Issue Keys. I have marked them as such in the attached spreadsheet Issues2Fix.xlsx.

These are the issues I would like to have saved:

These are the issue that can be removed--I will recreate them in LDP:

  • UXPROD-37 Closed Ability to connect data warehouse to workflow engine for triggering reports based on logical conditions.
  • UXPROD-39 Closed Build reports based on custom lists
  • UXPROD-38 Open Allow HTTP request for results of report/query
  • UXPROD-1866 Closed Create a reporting dashboard with canned reports
  • UXPROD-1875 Open Build a FOLIO Data Dictionary for reporting

(If none of them can be saved, we will have to re-create them all. I have the JIRA data to do so.)



 Comments   
Comment by Holly Mistlebauer [ 02/May/19 ]

Jakub Skoczen and Cate Boerema: I created this issue in the FOLIO project because I couldn't find a JIRA Configuration project. Today I uncovered the source of the problem. I am not sure of the solution given this is a duplicate Issue Key situation. I will do some digging. Thanks!

Comment by Holly Mistlebauer [ 02/May/19 ]

Never mind! I just fixed this problem! I couldn’t edit these issues, but found that I could do a bulk edit. So, I bulk edited these issues one by one to move them back to the LDP project…

UXPROD-37 Closed Now UXPROD-1869 Open Ability to connect data warehouse to workflow engine for triggering reports based on logical conditions (was UXPROD-1869 Open before move to LDP—JIRA brought it back to UXPROD and assigned Issue Key already in use)
UXPROD-39 Closed Now UXPROD-1867 Open Build reports based on custom lists (was UXPROD-1867 Open before move to LDP—JIRA brought it back to UXPROD and assigned Issue Key already in use)
UXPROD-38 Open Now UXPROD-1868 Open Allow HTTP request for results of report/query (was UXPROD-1868 Open before move to LDP—JIRA brought it back to UXPROD and assigned Issue Key already in use)
UXPROD-1866 Closed Now UXPROD-1866 Closed Create a reporting dashboard with canned reports (was UXPROD-1866 Closed before move to LDP—JIRA brought it back to UXPROD and assigned Issue Key already in use)
UXPROD-1875 Open Now UXPROD-1875 Open Build a FOLIO Data Dictionary for reporting (was UXPROD-1875 Open before move to LDP—JIRA brought it back to UXPROD and assigned Issue Key already in use)

…and these issues started opening up again…

UXPROD-37 Closed Limit/scope for permission assignments (PO Tania Fersenheim)
UXPROD-38 Open Expiration Dates for Addresses/Email/Phone Numbers (PO Tania Fersenheim)
UXPROD-39 Closed Local password management (PO Khalilah Gambrell--in Aster release)
UXPROD-1866 Closed Create internal Folio metadata format (PO Charlotte Whitt)
UXPROD-1875 Open Link metadata record to source record (PO Unassigned)

Sorry to have bugged you with this…

Generated at Thu Feb 08 23:17:27 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.