| The content of the JIRA macro is the list of issues to show: one issue key per line with the default list source, or a JQL query with the jql source. The Edit Macro dialog shows it as a plain text area, so the user has to know the issue keys and type them by hand, with nothing checking that they exist. The content is declared in JIRAMacro.java, with a DefaultContentDescriptor of type String. The main problem:
- For the list source, an issue picker suggesting the issues of the configured JIRA server could fill the content, one key per line, while a JQL query keeps a text area. Since the content takes one or the other depending on the source, the picker has to follow the source parameter.
Depends on The Edit Macro dialog always shows the macro content as a text area, whatever its declared type, so the picker cannot be offered before:
- XWIKI-23059, which lets the macro content use a displayer chosen from its type, like the parameters.
KOs covered
| Macro |
Criterion |
Parameter |
Problem |
Depends on |
| jira |
C4 input-assistance |
$content |
A plain text area, for issue keys as well as a JQL query. For the list source, the default, an issue picker with suggestions from the server could be used; a JQL query needs a text area, but nothing helps writing it. |
XWIKI-23059 |
Impact found on macro fluidity This KO comes from the WYSIWYG usability audit of the macros, under the criterion C4 input-assistance of its usability criteria. The page of the macro, linked in the table, has the full notes. Fixing it means declaring a content type for the JIRA macro and providing the displayer of that type, once XWIKI-23059 lets the content use one. |
