Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
11.1.7
-
None
-
Unknown
-
Description
The Edit Macro dialog of the JIRA macro puts the server, without which nothing renders, in the second tab, sorts the optional fields alphabetically so the parameters of the examples come last, and preselects {} in the parameters field.
KOs covered
| Macro | Criterion | Parameters | Problem |
|---|---|---|---|
| jira | C5 groups | URL | URL and id, the server without which nothing renders, are in the second tab, "Instance", after the "Optional parameters" tab, which holds the display options. |
| jira | C5 groups | id | In the second tab, "Instance", with URL, see the notes of URL. |
| jira | C3 defaults | parameters | The field preselects "{}", the Java rendering of an empty set of properties, instead of an empty field. |
| jira | C8 advanced | parameters | Rarely used, for internal settings like the label of the url field, and set by no example of the documentation, but not marked as advanced. |
| jira | C6 order | source | The documentation sets it in three examples, but it comes fourth in the Optional parameters tab, after maxCount and parameters, which no example sets: the order is alphabetical. |
| jira | C6 order | style | The documentation sets it in three examples, but it comes last in the Optional parameters tab, after maxCount and parameters, which no example sets: the order is alphabetical. |
Impact found on macro fluidity
These 6 KOs come from the WYSIWYG usability audit of the macros, under the criteria C3 defaults, C5 groups, C6 order, C8 advanced of its usability criteria. The page of each macro, linked in the table, has the full notes and the steps to reproduce. Fixing them means changing the parameter declarations of the macros: their groups, order, default values, mandatory and advanced flags.