Create a Dashboard to see all open tasks assigned to you or your team (One Task Board)

In your daily work you usually work your planned work with Jira issues and in addition you collaboratively work with your team members on tasks in Confluence. Usually in each session a Confluence task in created for some of you. Use the TaskONE macro to show all open tasks assigned to you to improve your own task management in Jira and Confluence. If a Confluence task is not processed, just create a Jira issue out of it and solve the Confluence task. 


Step-by-Step Guide

Define your TaskONE Confluence macro

To create a One Task Board with TaskONE follow these little steps. You can configure any deviation from this example if it suits your use case better.

Step  ProcedureExampleDescription

Generate a Confluence page named One Task Board


Add TaskONE macro to the page and open the Macro configuration.


Configure the Confluence tasks in TaskONE, so that it shows all open Confluence tasks for a specific user.

In this example we identify the relevant Confluence tasks via the assignee through all Confluence Spaces. 

Assigned toSam Anger
Task statusincomplete

Configure the Jira issues in TaskONE, so that it shows all open Jira issues for a specific user (e.g. all form a specific Jira board).

In this example we define the correct Jira Instance, because multiple Jira Instances can be linked to one Confluence. Afterwards we defined a JQL to match all relevant issues assigned to a specific User. We added the check for the status category to only get open issues. 

Jira Application LinkJira Blue
Jira Query Language (JQL)

assignee in (sam.anger) AND statusCategory not in (Done)


Further define the TaskONE Macro View, so that the relevant data is displayed and the sorting of your tasks is by due date.

In this example we have all tasks for a specific users, which need to be solved by due date. Therefore we added the reporter and the source, so that the users knows where to get more information about the task. With this the assignee can work from the top to the bottom. 

If a task is too big, they can simply create a plannable Jira issue via the Create issue function from Confluence. 
Number of tasks per page10
Columns to displaytasktype, description, duedate, reporteravatar, reporter, location
Sort byduedate

Save the configuration from TaskONE and add other macros as you wish (e.g. User profile for the assignee of all tasks in the configured list and a Panel macro to highlight the board). 

We recommend that TaskONE is the center of one page, because of its list view, but feel free to add other macros to aid your process. In this example we added the User profil macro containing the configured assignee in TaskONE. In this way we can remove the column assignee from the TaskONE Macro View and can still see that the One Task Board is for Sam Anger.

Further information → Atlassian documentation: User profile macro

7Publish your Confluence page. 

Check your changes and build your own One Task Board

Set Due dates automatically in Jira (optional) 

Use Jira Automation to set up automatic rules for your Due date. For example you can sync the End date of the Sprint with the due date of issues in that sprint. 

Jira Automation can be administrated by Project Administrators for their Project or for the global Jira Instance. If you have not enough rights contact your Administrators. 

Further information → Atlassian documentation: Jira automation - Data Center and Server


Go to Jira and add an Automation to set the End date of the Sprint as Due date to all related issues, when the Sprint is started. 


Go to Jira and add an Automation to set the End date of the Sprint as Due date to an issue, when the related Sprint of the issue changes.


Go to Jira and add an Automation to set the Due date of an issue, when the issue is created.