Reporting Bugs & Requesting Features

For All Non-Power Employees: Please report an issue through our github issues.

---

Discuss your issue in the Playbook Channel in Connect.

Ask yourself these questions first:

If your issue is a bug:

1. Use the Playbook Bug Report to gather the required information.

2. Confirm your findings in the Playbook Channel in Connect.

3. Work with UX Engineers as they troubleshoot. This may include:

• Highlighting things you've already tried.
• Pairing over a zoom call.
• Collaborating outside of the Playbook channel.

4. Collaborating on a Runway Ticket

• The Playbook Producteer will open a story on the backlog
• The Playbook Producteer will add the Nitro dev as a reviewer.
• The Playbook Producteer will add the UX Designer as a reviewer.
• The Playbook Producteer or UX Engineer will copy your Playbook Bug Report and paste it directly into the Runway Story where it can be tracked by stakeholders.
• If you are a UX Designer review the steps for making a handoff.

If your issue is a feature request:

1. A UX Designer should be your first point of contact. Reach out to the designer on your team. Your UX Designer will bring the request back to the Playbook Team in our Nitro UX channel for discussion. The whole UX team works extremely hard to make sure that what goes into Playbook, belongs in Playbook. The Playbook Team will determine if more action is needed and will follow-up with your request.

2. After the feature request has been vetted by design team, we will make a feature story.

3. Adding to the Playbook Backlog in Runway

• The Playbook Producteer will open a story on the backlog.
• If you are a UX Designer review the steps for making a handoff.
• The Playbook Producteer will add the Nitro dev as a reviewer.
• The Playbook Producteer will add the UX Designer as a reviewer.
• If needed, an investigative story for a UX Engineer will be made first