[OPENAM-16152] After upgrade, new Identity page has duplicate 'new identity' field and email address does not save Created: 22/Apr/20 Updated: 05/Nov/20 Resolved: 24/Aug/20
|Affects Version/s:||18.104.22.168, 7.0.0, 6.5.3|
|Fix Version/s:||6.5.3, 7.1.0, 7.0.1|
|Reporter:||Lawrence Yarham||Assignee:||Michael Carter|
|Labels:||AME, IAM, Must-FIx, Newton, release-notes|
|Σ Remaining Estimate:||Not Specified||Remaining Estimate:||Not Specified|
|Σ Time Spent:||Not Specified||Time Spent:||Not Specified|
|Σ Original Estimate:||Not Specified||Original Estimate:||Not Specified|
|Attachments:||Screen Shot 2020-04-21 at 4.57.02 PM.png|
|Sprint:||AM 2020.11 - Trip Hammer|
|Epic Link:||7.0.0 Post-Release|
After an upgrade from 22.214.171.124, the Identities -> New Identity page is displaying more fields that previously, has two 'User ID' fields, and specifying an email address does not result in it being saved when the identity is created.
|Comment by Andrew Vinall [ 22/Apr/20 ]|
Lawrence Yarham Was this an upgrade or clean install?
|Comment by Craig Gering [ 21/Jul/20 ]|
waiting for verification that this is problem on backend due to upgrade & not ui specific problem
|Comment by Michael Carter [ 13/Aug/20 ]|
Both Dipu Seminlal and I were unable to recreate this going from 6.5.0 > 7.x.0. It seems to only affect upgrades from 126.96.36.199.
|Comment by Adam Heath [ 24/Aug/20 ]|
Re-opening to transition issue status to "Resolved". Please can JIRAs be marked as "Resolved" rather than "Closed" when complete, especially when impacting older versions as well, as otherwise the JIRA can no longer be edited to update target/fix versions when backporting issues.