...
Issues displayed in the macro can be defined and added by setting up the scope configuration.
...
| Info |
|---|
Starting from version 1.0.77, all scopes can be edited & removed from the macro directly from the page view. Only adding a scope to the macro requires going into the page editor. |
...
JQL scope
JQLscope. Setting up a JQL scope will return issues within one JQLquery. The query is predefined in macro edit dialogue:
...
Manual scope
Manualscopealso allows to return issues from a JQL query. However, the JQL query is not pre-configured in the same way as for the JQL scope. Instead, users can add issues returned by multiple JQL queries. This can be done either from the ‘Edit macro’ dialogue or directly from the page view. 
Manual scope has a limit of 750 issues.
...
Manual scope: removing issues
To remove a single issue from the table, hover over the right end of the issue table to reveal a three-dot icon. Click the button to open the ‘Actions’ menu with an option to remove the issue from the table. Issues can be removed by users directly from the page view on in the ‘Edit macro’ dialogue.
...
Confluence tasks
This scope allows us to get a list of all Confluence tasks in the instance. The tasks table is displayed with 4 default columns: Description, Assignee, Due Date and Page (parent page of the task).
Default values for the ‘Create new issue’ dialogue
When users create a new issue from macro, they see and edit the ‘Create issue’ dialogue. The ‘Default field values’ configuration field allows to the pre-populate population of certain fields with a particular value.
To configure, first, select a custom field in the ‘Default field values’ drop-down.
Then, click on the ⚙️ icon. In the pop-up tab, you can set default values for each of the selected fieldsfield.
...
Table columns
In the issue table, columns represent the issue fields. A wide range of system and custom fields is available to add, view and edit via our macro. See Issue fields supported in macro for the list of supported fields.
...