Tutorials

Tutorial: Raising and Resolving Issues

In this tutorial, you will raise a structural defect as an issue, assign it to a team member, attach an annotated photo, track the resolution, and verify the fix. By the end, you will understand the full issue lifecycle β€” from raised to closed.

This tutorial assumes you have a Pasco Cloud account with access to at least one project and another team member you can assign issues to.


Before You Start

Make sure you have:

  • A Pasco Cloud account with access to a project.
  • At least one other team member in the project (so you can assign the issue).
  • A photo of a defect on your device (or you can use any test image).

Step 1: Navigate to Issues

Ginger Bear mascot

πŸš€ Let's go!

Open the Pasco Cloud web app and click Issues in the sidebar. You will see the issues list β€” if this is your first issue, the list will be empty.

Click the Create Issue button to open the creation modal.


Step 2: Fill In the Issue Details

Ginger Bear mascot

πŸš€ Let's go!

Fill in the following fields:

  • Title β€” enter "Cracked concrete in basement level 2" (or any descriptive title for your test issue).
  • Category β€” select Structural from the dropdown.
  • Priority β€” select High.
  • Project β€” choose your project from the dropdown.
  • Assignee β€” select a team member who will be responsible for the fix.
  • Due date β€” set a date one week from now.

The close-out manager defaults to you (the creator). This means you will be the one who verifies the fix at the end.


Step 3: Set the GPS Location

Ginger Bear mascot

πŸš€ Let's go!

In the Location section of the creation modal:

  • Location description β€” type "Basement level 2, column B3, south face".
  • GPS location β€” click the map picker and drop a pin at the approximate location. On mobile, you can tap Current Location to use your device's GPS coordinates.

The GPS location will appear on the issue's map view and on the detail page as an inline map.


Step 4: Attach and Annotate a Photo

Ginger Bear mascot

πŸš€ Let's go!

In the Attachments section:

  1. Click the upload area and select your defect photo (or drag and drop it).
  2. Once uploaded, click the Annotate button on the image thumbnail.
  3. The annotation editor opens. Draw a red arrow pointing to the crack.
  4. Add a text label that reads "50mm structural crack β€” requires assessment".
  5. Save the annotation.

You now have both the original photo and the annotated version attached to the issue.

[Screenshot: Issue creation modal with a title, category set to Structural, priority set to High, and an annotated photo showing a red arrow pointing to a crack]
Creating an issue with an annotated defect photo.

Step 5: Create the Issue

Ginger Bear mascot

πŸš€ Let's go!

Review your issue details and click Create.

The issue is created with Raised status. Your assigned team member receives a notification alerting them to the new issue.


Step 6: View the Assignee's Perspective

Now let us see what the assignee experiences.

Ginger Bear mascot

πŸš€ Let's go!

When the assignee logs in, they see a notification about the new issue. Clicking the notification takes them directly to the issue detail page, where they can see:

  • The issue title, description, and priority.
  • The annotated photo showing exactly where the crack is.
  • The location card with an inline map showing the GPS pin.
  • The due date.

The assignee can now visit the site, locate the exact spot using the GPS pin and location description, and assess the defect.


Step 7: Move to Open

Ginger Bear mascot

πŸš€ Let's go!

The assignee clicks the Open status action button to indicate they are now actively working on the issue. The status changes from Raised to Open.

This status change is recorded in the audit trail, and the creator and close-out manager are notified.


Step 8: Add a Resolution Comment

Ginger Bear mascot

πŸš€ Let's go!

After completing the repair work, the assignee adds a comment documenting what was done:

  1. Scroll to the Comments section on the issue detail page.
  2. Type a comment: "Crack repaired with epoxy injection. Structural engineer has inspected and approved the repair method."
  3. Attach a photo of the completed repair using the comment attachment button.
  4. Click Post.

The comment with the repair photo now appears in the issue timeline.


Step 9: Mark as Resolved

Ginger Bear mascot

πŸš€ Let's go!

The assignee clicks the Resolve status action button. The status changes from Open to Resolved.

The close-out manager (you, the creator) receives a notification that the issue has been resolved and is ready for verification.


Step 10: Verify and Close

This is your step β€” the close-out manager verifies the fix.

Ginger Bear mascot

πŸš€ Let's go!

Open the issue detail page. You can see:

  • The assignee's comment with the repair photo.
  • The audit trail showing every status change with timestamps.
  • The original defect photo for comparison.

If the fix is satisfactory, click the Close status action button. The issue status changes to Closed, and the issue is complete.

If the fix is not adequate, click Reopen to send the issue back to Open status. Add a comment explaining what still needs to be done.


Step 11: Review the Audit Trail

Ginger Bear mascot

πŸš€ Let's go!

Scroll through the issue detail page to see the complete audit trail:

  1. Issue created β€” with your name and timestamp.
  2. Status changed to Open β€” by the assignee, with timestamp.
  3. Comment posted β€” the assignee's resolution note with repair photo.
  4. Status changed to Resolved β€” by the assignee.
  5. Status changed to Closed β€” by you (the close-out manager).

This creates a complete, timestamped record of the issue from identification through to verified resolution.

[Screenshot: Issue detail page showing the complete audit trail β€” creation, status changes, comments with photos, and final closure]
The complete audit trail β€” every action recorded with timestamps.

Bonus: Issues from Report Fields

Issues can also be created automatically from flagged report responses. Here is how it works:

Ginger Bear mascot

πŸš€ Let's go!

  1. Open a report in the builder that uses a template with flag logic configured (for example, a Pass/Fail inspection checklist).
  2. Select Fail on an inspection item.
  3. If the template has "Raise Issue" enabled on that field, you will see a Raise Issue button appear.
  4. Click it to open a quick issue creation modal. The title is pre-filled from the field label (for example, "Roof framing alignment β€” Fail").
  5. Set the priority, assignee, and any other details, then create the issue.

The issue is now linked to the report β€” you can navigate from the issue to the source report, and from the report to the linked issue. This creates a direct chain of evidence from the inspection to the corrective action.


What You Have Accomplished

In this tutorial, you:

  • Created an issue with a descriptive title, category, priority, and due date.
  • Set a GPS location so the issue can be found on the map view.
  • Attached and annotated a defect photo.
  • Tracked the issue through its lifecycle β€” raised, open, resolved, closed.
  • Verified the fix as the close-out manager.
  • Reviewed the complete audit trail.
  • Learned how issues can be created from flagged report responses.

What's Next?

  • Want to manage day-to-day work items? See the Tasks Overview for tracking action items, deadlines, and responsibilities.
  • Need a visual workflow? Learn about the Kanban Board for task management.
  • Looking for contract tracking? See the Contracts Overview.
Previous
Completing Your First Report