Issues - Introduction
Issues (also known as punch list items) serve a central role in Bluerithm. They allow you to not only manage and track internal issues and critical items on your projects, they provide a means to manage and track other people’s issues who are outside of your organization – your guest users. This could be subcontractors, or a host of people and companies on a project who’s work you are responsible for verifying and checking.
Issues can be attached to equipment, the project, and work items.
Issue Identifier: The Issue Identifier can be whatever you’d like it to be. By default, it’s automatically incremented when you create a new issue. The issue prefix can be changed from the Details pane of the Settings page of a project.
Status of Issue: This is the status you are responsible for as the owner or creator of an issue. You set this manually based on the actual status of the work associated with the issue, however, it will automatically change from ‘open’ to ‘awaiting verification’ if the respondent, which is who you’ve assigned the issue to, updates the Respondent Status to ‘complete’. It is then up to you to verify their claim, then set the status to ‘closed’ if the action taken is satisfactory.
Description: This is the description of what the issue is and why it was recorded.
Due Date: The date the issue is needed to be resolved by. This could be based on internal reasons, or constraints of the project.
Entered By and Last Edit: The dates the issue was entered or edited, and by who.
Respondent Status: The status that the respondent, which is who the issue is assigned to, can set. As mentioned above, this can trigger the issue owner status to ‘awaiting verification’ if the respondent changes it from ‘open’ to ‘closed’.
Assigned To Company and Person: The person and their company who the issue is assigned to. When Shared Issues and Work is turned on for a company, assigning an issue to an individual means it's assigned to anyone from that company.
Estimated Effort: The estimated amount of time involved in correcting the issue. You set this when you create the issue. This is a field the respondent can edit.
Last Respondent Edit By and Date: The last person from the responding company to edit the issue, and the date the edit occurred on.
How Issues Work
Issues are designed to be a point of collaboration in BlueRithm. That means they are accessible to the person and company that created them, as well as by who they’re assigned to, and anyone who has full access to a project.
Users from the company of the person who created the issue can edit all fields in the issue.
Users from the company who the issue is assigned to have access to only the following:
- Respondent Status
- Add a Response or File
Users with the following Roles can add issues:
- Account Admin
- Privileged Guest
An issue (or notes or files added to an issue) can only be edited or removed by who created it, with the exception of users with the Role ‘Account Admin,’ who can remove issues created by anyone.
Custom Issue Properties
You can add custom issue properties to your projects.
Go to the Settings > Issue Properties page of any project, and add custom issue properties as needed.
Bulk Operations on Issues