Issue Summary

The field Priority gets duplicated in the issue view after the agent assigns the ticket.

Steps to Reproduce

SCENARIO SETUP

1. Have 2 request types associated with the same issue type; (let's call R1 and R2 from now on).
2. Have both requests with almost all the same fields in the Issue view and Request form tab;
3. In the R1, add a Select List (cascading) field type to the Issue view tab, in my case, the field is the Operational Categorization.
4. In the R2, add the Priority field in place of the Operational Categorization, in the Issue view tab.

4. Add the same Operational Categorization field to the R2's Request form instead of the Issue view as in R1:

5. Now create a single automation rule that adds a comment to the issue whenever the ticket is assigned to an agent:

PS: This is an optional step since it is easier to trigger the partial refresh using automation rules. However, any process that causes a partial refresh will cause the bug.

PROVOKING THE BUG

1. Create an issue using the R1 type (the Operational Categorization field SHOULD NOT appear in the creation screen);
2. Now, access the just-created issue and change the value of the Operational Categorization field to any combination.
3. Then, change the Request type from R1 to R2;
4. Now, assign the ticket and trigger the automation (or just assign if this refreshes the page in your case).
5. This will cause the issue screen to partially refresh and duplicate the Priority field.

Expected Results

The fields to swap positions without duplicating.

Actual Results

The Priority field gets duplicated when swapped.

Workaround

This is a temporary visual bug. As soon as the agent refreshes the page, the bug disappears.