...
When first added to the page, the macro will be empty, with no issues displayed.
...
Adding issues to the macro: scope configuration
Issues displayed in the macro
...
There are 2 options for adding issues to the macro. Issue displayed in macro are defined via ‘Scope’ configuration. There are 2 scopes:
‘JQL' scope - allows to include issues returned via a JQL query. Can also be set via the ‘Add existing issues’ button in the
panel. ‘Manual’ scope - prompts a create issue dialogue. After saving, the new issues will be displayed in the preview. Can also be set via the ‘Create issue’ in the
panel.
...
Manual scope
To keep adding issues in the manual scope click the ➕ icon at the beginning of the table row. When selected the button opens a menu with options to create a new issue or add existing ones (via JQL).
...
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 in the ‘Edit macro’ dialogue.
...
Columns Display
Project, Issue Type and Summary are the default fields any macro is always required to have. Otherwise, feel free to choose as many as needed from a fetched selection of your Jira fields.
Application Link
Application links let you integrate Confluence with another Atlassian product or external application so they can exchange information, resources, and functionalities. What exactly is exchanged will depend on the applications you link. You learn more about it here. Once you will connect more than once products here you will have an option to select where you want to have your data fetched from.
Issues per age
Define how many issues shall be displayed before pagination rolls in.
Issue Creation Row
Create a new Jira issue straight from your Macro. Have an additional row configured for this purpose and select where it should be displayed: above or below the table.
Order by
Choose a preferred subject of sorting. To enable manual drag and drop sorting choose Order by Rank.
...
| panelIconId | atlassian-info |
|---|---|
| panelIcon | :info: |
| bgColor | #FFFAE6 |
...
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 the pre-population of certain fields with a particular value.
To configure, 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 selected field.
...
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.
To add a column, select a custom field in the ‘Column display’ drop-down list. The added field will be immediately available in the preview.
...
Table pagination
In the ‘Issues per page’ configuration field, users can determine the number of issues that will appear on the screen before pagination is activated.
Default ordering
In the 'Order by' configuration field, users have the option to choose a custom field to sort table rows based on custom field values.
Sorting direction
A checkbox ‘Reverse order’ gives an option to define the direction of sorting.
To sort issues in ascending order, leave the box unchecked. Check the box to sort issues in descending order.
...
This configuration is available only for a JQL scope.