Introduction

The Near Digital Collective encourages community involvement in its software development and maintenance efforts. A critical aspect of this is the identification and resolution of bugs, as well as the suggestion and integration of new features. This process, known as bug triage or feature addition, is made more seamless and interactive through the use of Canny.io, a user feedback management tool.

This document provides an in-depth overview of the bug triage and feature addition process with the utilization of Canny.io, specifically through the Near Digital Collective's Bugs and Feature Requests Board.

Process Flow Chart

https://miro.com/app/board/uXjVM9Q5GR0=/?share_link_id=977727981641

Step 1: Issue Identification and Checking

Before reporting a new issue or feature:

• Check Existing Issues: Browse through the existing entries on the Bugs and Feature Requests Board to see if the issue or feature you have identified has already been reported.
• Upvote Existing Issue: If the issue or feature has already been submitted by another user, support it by upvoting the existing post. This helps prioritize the most critical issues and desired features.

Step 2: Issue Reporting on Canny.io

If the issue or feature has not been reported before, proceed with the following:

• Bug Description/Feature Explanation: The individual identifying the bug provides a detailed description of the bug and the steps to reproduce it. For a proposed feature, a detailed explanation should be provided along with potential benefits and use cases.
• Visual Aid: Where possible, screenshots or other relevant images should be included to further illustrate the issue or feature.
• Issue Submission on Canny.io: The bug description or feature proposal is submitted on the Bugs and Feature Requests Board.

Step 3: Initial Assessment