Classifying and structuring issues

Classifying and structuring issues

To be able to organize and structure the issues, it is necessary to define as many properties as possible. The more detail an issue contains, the better to situate it and work with it.
Start by defining the issue's Type, Area, Milestone, Labels, Priority, Assigned to and Custom fields.
  1. Type can help you distinguish between clashes, modeling errors, technical problems, inquiries, and others.
  2. Area can help you categorize problems by location. This is a very useful setting when working on a large project. The project leader has the possibility of defining a different owner per area. When a new issue is created in an area, it can be automatically assigned to the owner of the area concerned.
  3. Milestone can be set to define project fase of the issue. A milestone is defined by the project leader with a name, start date and end date.
  4. Labels provide more freedom in classifying issues. They can be used to mark the different disciplines and other things.
  5. Priority defines the importance of the issue. When this is set by the one who creates the issue, it helps to define which issues should be handled first by the team members.
  6. Assigned to should show the team member who is next to handle the issue. When he is done, the assigned to can change to a different team member to pick it up next. There can only be one team member assigned to an issue at the same time, to ensure there is always someone responsible for this issue.
  7. Custom fields can be added by the project leader if there is a need to have more properties to define and filter the issues.
All of these properties can be defined and edited by the project leader according to the needs of the project.
Custom fields are a feature of the Premium and Ultimate plan.
The filter makes it possible to show similar issues while working in the project. Learn more about Managing issues with filters in this article.

Next, the status of an issue will change throughout its life cycle. There are three options available for the status of an issue: Active, Resolved, and Closed.
You will not be able to change these titles or add other additional statuses.
  1. New issues always start out as Active
  2. After solutions are found to an Active problem, you can resolve it so that it becomes Resolved, or "resolve and close" it so that it becomes immediately Closed
  3. Resolved issues can be reactivated or closed and will turn back to Active or change to Closed
  4. Closed issues can be reopened when necessary to become Active again

In a Premium or Ultimate plan, you will have access to a more formal workflow that allows you to add an approval workflow to the issues. The three options available for the status will remain the same, but an issue may carry additional team member(s) which need to approve the solution when the issue is resolved.
  1. When the 'Approval' field is assigned in the properties of an issue, and this issue changes from Active to Resolved, it will need to be approved by the indicated team member(s).
  2. The approver will have the choice to reject the solution for the issue so that it becomes Active again, or to approve the solution so that the problem acquires the status Resolved, approved;
  3. The Resolved and approved issue can then be Closed or Rejected to become Active again.
It is possible for an issue's resolution to be approved and / or rejected by one or more team members before the issue is closed.

For more information about the approval workflow, consult the article The approval workflow.

    • Related Articles

    • Create references to other issues

      When one issue needs to be mentioned in another, the hashtag symbol (#) can be used to create a hyperlink and facilitate navigation to the referred issue: Open the issue you want to edit in edit mode  Go to the 'Comment' field Type '#' followed by ...
    • Assign issues to a generic user like ARC or MEP

      Although it is not recommended, it is possible to assign problems to a generic user like ARC or MEP. To do this, you must create a special user. This user does not need to be active, but a valid e-mail address is required. When you want multiple ...
    • Use the activity log to see what is going on with your issues

      BIMcollab Nexus keeps track of all changes made to the issues in your project. To see a summary of the latest activities of every project on the My Projects page, show the projects in the List view. You can click on the changes in the list to go to ...
    • Automatically assign issues based on the selected Area

      When creating or editing an issue, you can automatically assign it to a user of you choice by setting an area for the issue. To do this, you first need to select an area owner for that area. Go to the Settings page of your project and select 'Areas' ...
    • Colors of issues based on their status

      The title of issues in BIMcollab Nexus, BCF Managers, and BIMcollab Zoom will be in different color based on their progress status. Read more about approval workflow and progress status in Classifying and Structuring Issues. The issues can have the ...