[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: |
|
||||||||
| Issue links: |
|
||||||||
| 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
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: 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:
(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…
…and these issues started opening up again…
Sorry to have bugged you with this… |