Github Issues Overivew

This document is an outline of how we are using the Issues feature on Github to track work.

Overview

We are using Github Issues primarily to track bug reports. If you find a new bug while using Safe Paths, please document it with an Issue! Make sure to fill out the template as accurately as possible, and please stay involved as the issue is worked on.

Best Practices

Please follow these best practices when creating a new issue:

• Make sure that you are testing against the latest code from the develop branch
• Write the issue title in a proper, short, descriptive way. E.g. [Settings] - Location Active/Inactive toggle not displaying proper status
• Fill out all of the fields in the Issues Template
• Add relevant labels

Feature Requests

If you have a request for a new feature in Safe Paths, please do not submit a Github Issue.

In order to document your request and ensure that it gets in front of the right teams, please join our Slack workspace and submit a post on the #ideas channel.

Jira

The majority of feature work being done on Safe Paths is tracked/managed in Jira. This is where we create our sprints, interact with UI/UX teams, etc.

If you would like to be added to Jira & Slack to view our ongoing workstreams, please fill out the Volunteer Intake Form. If you need assistance joining our team, please reach out to Jay Summet at [email protected].