Select a topic from an topic board a to open the topic page of the topic.

This is what the topic banner on the topic page can look like:

The topic header can be found below the banner and will be discussed in this article:

Below the topic header the topic body can be found with description and comments.

To the right of the topic body and header the right information panel can be found.

Click on th information icon in the topic banner to expand the right infomraiton panel.

This article contains information about the following topics:

Highest up in the topic header the title/subject of the topic can be seen.

Next to the title a pencil icon can be seen.

This pencil icon can be uses to change the name of the topic.

Access required: Write access to the topic board the topic is in

Depending on the settings that are set by users with full access to the topic board, statuses and types can be configured in different ways in the topic board settings.
The top status or type will always be default and can be changed before submitting the topic.
The order of the statuses and types in the dropdown list can also be set by the configurator.

Here the current status of the topic can be chosen.

The default statuses that can be choosen between are:

Active (Open)

In-progress (Open)

Resolved (Open)

Approved (Closed)

Rejected (Closed)

You can edit these or create your own statuses.

When should each status be applied?

Typically new topics that get created receive the status open.
Optionally a candidate status can be chosen if the topic that is submitted falls outside of the typical open and closed flow.

An example of this can be:

The topic creator is not done editing.

The topic so it is not ready to be opened yet in this case.

The topic is no longer relevant.

The topic is not relevant at the

or when the topic is not relevant any more

Then when the topic has been handled by the assigned user the person verifying that the topic has been handled will change the status to closed.

Here you choose the type of topic you are creating.

The default types you can choose between are Error, Warning, Info and Unknown.

You can also create your own types.

In the assigned to and requested by fields a member or a team can be selected to be set as assignee or requestee from a dropdown menu.

It is often better to assign a topic to an individual member rather than a team as that member will feel personally responsible for following up on the topic and can be held accountable.

When a team is assigned none of the teammembers will feel personally responsible.

Still, there is often more than one member that is part of this conversation.

In this situation it is better to mention the members individually with @member or mention a team with @team in either a comment or the description of the topic.

This way the right person can be set as assignee and the other involved parties can properly be notified.

The member that is assigned does not neccessarily have to be the person that is responsible for carrying out tasks that are discussed in the topic but should be the one that is to follow up that the discussion results in a conclusion.

When a member is assigned the topic is shown on the member page of that member.

Clarifying concerned team with member@team

Members are often part of different teams depending on the different roles they have in the project.

By clarifying which team that the assignee is part of that this topic concerns the topic can be filtered better in the topic board.
Clarifying the team can both help members that are assigned to many topics to separate topics between their different roles as well as that it will help others find topics that concern this team.

When a member@team is assigned the topic is displayed on the team page of that team.

No notification is generated for team members when the concerned team is clarified.

Notification generated

Individually assigned assignees get a notification that they have been assigned to a topic. Additionally, they are automatically set as follower to the topic and thereby get notifications about future changes in the topic.

One drawback with assigning a member instead of a team is that only that member gets notifications about the topic.

This can be solved by mentioning other members in the description or comment so they automatically follow the topic and as a result get notifications about future changes in the topic.

Assign team or leave blank when follow up is unclear

It is often not enough to rely on a team to follow up on a topic as none of the team members will feel personally responsible for this task.

If it is not clear yet who will be responsible for following up on the topic assign a team so the team topics can be filtered for later assigning.

Only assign to a team when it is made clear that the team will come together to assign the topic to the right person.

Reasons for assigning a team can be because there is no one person in a team deciding responsibility.

If there is a team leader or similar that decides responsibility it is often best to assign them individually so they can delegate the responsibility when needed.

Notification generated

Unlike individually assigned members, who automatically follow the topic when assigned, members of an assigned team are not set as follower.
They get an initial notification of "a team you are part of is set as assignee", but will not get further notifications about changes in the topic.

If no member or team is responsible for following up on the topic the assignd to field can be left blank.

This can be when the topic is just for information.

Notification generated:

No teammembers are notified that a team they are part of are assigned to the topic and no members are notified that they are assigned to the topic nor will they get notifications about future updates unless they are mentioned, set as assignee or requestee or manually follow the topic.

Here you normally set yourself as requester, but you can choose any member here.

You would set someone else here if you were making the topic for someone else.

The requestee will automatically follow the topic and thereby get notifications about future changes in the topic.

If no member or team requests the topic the requested by field can be left blank.

Notification generated:

No teammembers are notified that a team they are part of requests the topic and no members will they get notifications about future updates unless they are mentioned, set as assignee or requestee or manually follow the topic.

Due dates and milestones can help you track progress on the statistics page.

Icon color

Icons for due dates and milestones can have different colors depending on time.

When setting a due date or milestone

The icon is the following color when the due date or milestone is set at this time:

A set due date or milestone works the same but is described differently.

The icon for a due date or for a milestone is the following color when it:

When a topic is closed the icon of a due date or a milestone is dim gray.

Due date

If there is an idea of when the content of the topic is due, set a due date or leave it blank.

It is often good to set a due date even if it is not clear exactly when the content of the topic is due.

The due date can always be changed later.

By getting in the habit of setting due dates the planning can be informed.

The more timeframes are speculated the more project members can anticipate.

Milestone

Pin the topic to a milestone or leave it blank.

A milestone in the topics area is often a project phase or the date of a planned event by which topics need to be delivered.

Add an existing label or enter a new one to create it.

Add your own fields to the headers of topics in an topic board.

These fields can be set as mandatory.

Custom fields can be of type: