Please note: This is a template that will undergo frequent updates so please copy this version at all times and don't reuse old templates.
Once a detailed feature is requested the feature will go through the following phases.
Feature Request: Recognition that the team has received this issue and is pending review.
Feature Review: The team is currently discussing wether to accept or reject this feature.
Feature Rejected: The team decided that this feature is not going to be integrated.
Feature Accepted : The team decided that this feature will be integrated and is under development.
Feature Complete: The team has completed this feature and it will be integrated in the next release.
Feature Shipped: The feature is completed and is in the current version and the issue can be archived.
It's important that you respond to any communication requests otherwise the issue may be rejected.
Template Example
Copy/Paste this template into a new request.Don't include the Feature Example .
## **Request**The feature request name
## **Current Problem**A description of the problem I have
## **Future Solution**A description of the solution I would like to see
## **Other information**If you have screenshots, designs, wireframes or other documentation please provide them here or simply say "No other information
Feature Example
Below is an example of how to request a feature.
Request
Add Address Book Functionality
Current Problem
I would like to save a list of addresses that I make frequent transfers/exchanges too. It's frustrating that I have to copy/paste the same addresses repetitively.
Future Solution
I would like to be able to go somewhere in the application and save addresses that I frequently use. It's important that I can name these addresses so they're easy to distinguish. I expect to be able to Create, Read, Update and Delete these address names within my address book.
Overview
Please note: This is a template that will undergo frequent updates so please copy this version at all times and don't reuse old templates.
Once a detailed feature is requested the feature will go through the following phases.
Feature Request: Recognition that the team has received this issue and is pendingreview.Feature Review: The team is currently discussing wether toacceptorrejectthis feature.Feature Rejected: The team decided that this feature is not going to be integrated.Feature Accepted: The team decided that this feature will be integrated and is under development.Feature Complete: The team has completed this feature and it will be integrated in the next release.Feature Shipped: The feature is completed and is in the current version and the issue can be archived.It's important that you respond to any communication requests otherwise the issue may be rejected.
Template Example
Copy/Paste this template into a new request. Don't include the Feature Example .
## **Request**The feature request name## **Current Problem**A description of the problem I have## **Future Solution**A description of the solution I would like to see## **Other information**If you have screenshots, designs, wireframes or other documentation please provide them here or simply say "No other informationFeature Example
Below is an example of how to request a feature.
Request
Add Address Book Functionality
Current Problem
I would like to save a list of addresses that I make frequent transfers/exchanges too. It's frustrating that I have to copy/paste the same addresses repetitively.
Future Solution
I would like to be able to go somewhere in the application and save addresses that I frequently use. It's important that I can name these addresses so they're easy to distinguish. I expect to be able to Create, Read, Update and Delete these address names within my address book.
Other Information
No other information