├── ISSUE_TEMPLATE
└── README.md


/ISSUE_TEMPLATE:
--------------------------------------------------------------------------------
 1 | ## Bug report form
 2 | ### Steps to reproduce
 3 | 1.
 4 | 2.
 5 | 3.
 6 | 
 7 | ### Expected behaviour
 8 | Tell us what should happen.
 9 | 
10 | ### Actual behaviour
11 | Tell us what happens instead.
12 | 
13 | ### Browser/system information
14 | Tell us which browser, browser version, and operating system you were using when
15 | you encountered this issue.
16 | 
17 | ### Additional details
18 | 
19 | 
20 | ## Feature Request Form
21 | ### Problem you are trying to address with this feature
22 | 
23 | ### Your solution
24 | 
25 | ### Add tags - did you add labels? 
26 | If this a customer requested feature, make sure to add that label. 
27 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # product-backlog
2 | Purpose: All new features, bugs, customer requests will be curated in this repo. We will use the issues created here to flesh out features, designs, and requirements. 
3 | 
4 | *What happens here, doesn't stay here*
5 | - The issues reported in this repo will be worked on in other Hypothesis repos. 
6 | - Issues created in #product-backlog will serve as parent cards that track all information about that request. 
7 | - All Google docs, PR info, or issues created in other repos must be linked back to issues created in this repo. 
8 | - We're implementing this system so that we can have complete transparency around our product developement process.
9 | 


--------------------------------------------------------------------------------