DO NOT DELETE HEADERS. THIS BREAKS AUTOMATION AND WILL CAUSE UNNECESSARY REJECTION OF THE REQUEST

1. Feature Overview (aka. Goal Summary)

random stuffs can be put here, but what we really want is useful information.

2. Technical Goals (aka. expected user outcomes)

Please describe what the feature will achieve from a technical perspective. What is the current state of the product being used and how would it change? Please try to outline clear, achievable goals.

Ugh does anyone else think that Jira is just extremely bad? Like why the heck did they even create this ui which is so darn bad?  

3. Business Goals (aka. expected user business requirements)

Please describe how the feature will impact the customer from a business perspective. What are the expected business requirements to consider during implementation of the feature enhancement and how would these impact user business.

I'm going to talk a little about business. Basically, customers will want to make money. Therefore, they pay us to help them make money by fixing things that they don't know how to fix themselves.

Background (Optional)

Provide any additional context is needed to frame the feature.

<your text here>

Use Cases (Optional):

_Include use case diagrams, main success scenarios, alternative flow scenarios.

<your text here>

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Please fill in, to the best of your knowledge, the following table.{color}