Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-4637

Renaming a persona or role in Epic Personas results in a duplicate name/role.


    • 1
    • Severity 3 - Minor
    • Yes
    • Add a duplicate entry validation to edited names and roles of personas.

      Issue Summary

      When modifying an existing Epic Persona, users can bypass the duplicate name validation of names and roles and rename an existing persona to an exact match of an existing user. This can cause ETL to fail in Enterprise Insights due to primary key duplication issues.

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Open Personas
      2. Open an existing persona with a unique name/role.
      3. Edit Persona's name or role to an exact duplicate to a different existing persona.
      4. Save the change.

      Expected Results

      An error identical to the error received when creating a new persona with a duplicate name/role tittle is created.

      Actual Results

      Name is saved and duplicate name/role data is committed to database, which causes primary key duplication issues with Enterprise Insights.


      If a user has committed a save with duplicate value, they can rename the duplicate entry in the user interface, then a manual truncate on that table needs to be run followed by manually launching the ETL job to restore Enterprise Insights functionality.

            dfuller@atlassian.com Don Fuller
            4359d07f7f4f Christopher Stringari
            0 Vote for this issue
            3 Start watching this issue