Page tree
Skip to end of metadata
Go to start of metadata


Projects in dynaBOARD are exactly the same as in JIRA. You only need to tell dynaBOARD, which projects you want to assign to your customers / teams.

Add project

In order to add a project to dynaBOARD, click on the Add Project button.

Project - select the project you want to add to dynaBOARD. If the list is empty, the API user has no project view rights (if you are using JIRA Server).

Board type - choose Scrum or Kanban, in accordance with JIRA. This influences how dynaBOARD gets and formats issues in sprints from JIRA. Make sure it corresponds with your JIRA setup, else dynaBOARD might display strange information about your sprints and issues. If you do not use boards, choose Kanban.

Click on Save when you are done. dynaBOARD will then fetch the required project key information from JIRA, and make a basic setup. Repeat this for all the projects you intend to show in dynaBOARD.

Project overview

The overview list shows you all the projects you have added to dynaBOARD. These are invisible to customers / teams, until you actively assign the projects to them in the customer administration.

Key - the project key from JIRA.

Name - the project name from JIRA.

PJM-ID - this is the id of the project in your JIRA instance. It is for reference only.

Board type - either Kanban or Scrum, as set by you when first added the project.

Status approvable - the status in which dynaBOARD recognizes the issue as being in an approvable status for your customers / teams. Is empty after adding, edit the project to change it (see below).

Status approved - the status in which dynaBOARD moves the issue once it has been approved by your customers / teams. Is empty after adding, edit the project to change it (see below).

Status disapproved - the status in which dynaBOARD moves the issue once it has been disapproved by your customers / teams. Is empty after adding, edit the project to change it (see below).

Status - shows if the project is active or inactive. Inactive projects are not shown to users, reports are not generated, etc.

Actions - allows you to

  • resynchronize - if some parameters of the project changed in JIRA, e.g. new status types, changes status names, etc.
  • edit - allows you to edit the project properties (see below)
  • delete - removes the project from dynaBOARD, and all references to it. Does not delete the project in JIRA.

Edit project

Editing the project allows you to configure some more settings than at the time of adding the project.

General properties

Here you can change the board type and the status.

By default, dynaBOARD determines if an issue has been resolved ("definition of done") by the resolution field. If it is filled, the issue is considered done/solved. Alternatively you can select a specific status for it. In this case choose "By status...", and select the status for done in the dropdown list below.

This influences progress bar display in issues view and some other parameters in dynaBOARD.

Issue approval

In this tab you can define the status for the approval system of dynaBOARD. If the user have the rights to use the approval system, dynaBOARD offers a separate menu item on the left hand menu for the users named "Approval". It resembles the Issues area, where you can search and filter issues. But this list only shows issues which are in the approvable status set here in this tab. The customers / teams then have the opportunity to approve and disapprove issues, and the destination status for these two workflow options can be set here, too.

Activate customer approval? - activate or deactivate the approval system for this project.

Status for approved by customer - select the status in which issues are considered to be ready for approval by customers / teams.

Status for approved issues - the destination status approved issues are automatically moved to.

Status for disapproved issues - the destination status disapproved issues are automatically moved to.

For more information about the approval of issues, please check the corresponding page in this documentation.


In this tab you may change the behavior of comments displayed in dynaBOARD.

Filter comments

This setting influences if comments should be filtered when showing them in dynaBOARD, or not. The following options are available:

  • no - filtering is not active, all comments will be shown
  • only show comments with starting tag - comments which have the tag (see below) right at the beginning of a comment will be shown; all others will be hidden.
  • hide comments with starting tag - comments which have the tag (see below) right at the beginning of a comment will be hidden; all others will be shown.


Important: no matter which option you choose for showing comments in dynaBOARD, all comments which originate from dynaBOARD will always be shown. This includes for example comments from customers through dynaBOARD (so they always see their own comments) as well as automated comments (see approvals).

Filtering tag

This sets the tag dynaBOARD is looking for when filtering comments. This tag has to be used in comments in your JIRA if you want to affect the display in dynaBOARD. A tag is suggested, but you may change it if you like. But be advised that the tag should be as unique as possible, to avoid it being used accidentally when writing comments in JIRA.

Example: you want specific comments to only appear in JIRA, as they are internal comments. So by setting the Filter comments to only show comments with starting tag you could avoid regular comments being shown in dynaBOARD. If you want the comment to be shown in dynaBOARD, you would prefix your comments with the tag in JIRA.

As the filtering is always based on the tag you choose, changing the tag will not affect old entries. So be careful with changes, as this might cause unwanted results.

The same is true with the portal name in the server version of dynaBOARD. It is used to parse the comments and check which one is a dynaBOARD generated comment - changing the portal name might also impact comment filtering. Also do not use the same name for portal and tag, as this might cause problems.

Generally, you should set the tag and portal name before opening dynaBOARD for your customers if you plan on using comment filtering.



  • No labels