Add fix for issue identified with editing custom fields where scheme id is not the same as fieldconfig id

XMLWordPrintable

      As identified here,

      https://support.atlassian.com/browse/JSP-7492

      It appears that the patched file corrects a long standing problem that can only be uncovered when the ids of fieldconfigurations and fieldconfgschemes are not the same for the same fields. Legend has it that the CSV importer could cause such a situation to occur (when importing non global custom fields) even though it can't be caused using the admin UI.

      Fix the the bug as per the patch on JSP-7492 and investigate the CSV importer bug.

              Assignee:
              Chris Mountford
              Reporter:
              Chris Mountford
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified