Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
11.1.7
-
None
-
Unknown
-
Description
The JIRA macro takes the source, the style and the fields in free text fields of the Edit Macro dialog, so the user has to know the accepted values, and a wrong one fails at rendering or renders nothing.
The main problems:
- The source and the style are fixed lists, which a Java enum would turn into a select with no other change: they do not depend on another ticket.
- The fields are the fields of the JIRA server, each with an optional label, written in a dedicated syntax: a multiple select of the fields of the server needs a provider.
Depends on
Most of these fields cannot be offered before these generic changes, each giving the macro the means to declare the expected value:
- XWIKI-23045, which lets a parameter get its values from a provider, with or without custom values.
KOs covered
| Macro | Criterion | Parameter | Problem | Depends on |
|---|---|---|---|---|
| jira | C4 input-assistance | source | A free text field for list or jql, where a select could be used: source="foo" is accepted and fails at rendering. | - |
| jira | C4 input-assistance | style | A free text field for table, list or enum, where a select could be used: style="foo" is accepted and fails at rendering. | - |
| jira | C4 input-assistance | fields | A free text field for a list of JIRA fields in a dedicated syntax, where a multiple select of the fields of the server, with an optional label, could be used. | XWIKI-23045 |
Impact found on macro fluidity
These 3 KOs come from the WYSIWYG usability audit of the macros, under the criterion C4 input-assistance 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 declaration of the parameters in the macro definitions.
Attachments
Issue Links
- depends on
-
-
- Open
-