-
Bug
-
Resolution: Fixed
-
Low
-
1
-
Severity 3 - Minor
-
Issue Summary
The order of an alert's Extra Property fields display inconsistently, compared with the order they are set in either the incoming data or the integration settings. Additionally, there is inconsistency in the order that these fields display in both the web and mobile apps.
Steps to Reproduce
- Create an alert with some extra property key/value pairs, with the keys in non-alphabetical order.
- View that alert in both the web and mobile apps, and compare the order of extra properties between them and the order that was set when the alert was created.
Expected Results
Either A) The extra property fields are displayed in both web and mobile in the same order that they were created (order is maintained), or B) that extra property fields are displayed in alphabetical order.
Actual Results
We see two different behaviors - in the web app, extra property values are displayed in alphabetical order (based on the key), while in the mobile app order appears to be random.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[OPSGENIE-20] Inconsistent order of alert Extra Property fields in web and mobile UI
Hi everyone,
This is Alp from the Opsgenie team. Thank you for your patience as we work on fixing this bug. We have identified the root cause for this bug, and we’re exploring solutions to address it. We will be providing any updates as they come. Thank you again for your patience!
Best,
Alp Gürtan
Hi everyone,
This is Alp from the Opsgenie team. This bug is fixed and I confirmed the functionality to be working as expected.
Sincerely,
Alp Gürtan