Feature Requests
A guide to submitting effective feature requests and getting the most from your development time.
What is a Feature?
Understanding what qualifies as a feature request.
A feature is new functionality that doesn't exist in your system yet. It adds capabilities your users don't currently have.
Features are the building blocks of your application. Each one should solve a specific problem or enable a particular workflow for your users.
Examples of features:
- Add ability for customers to download invoices as PDF
- Create a dashboard showing monthly sales statistics
- Add email notifications when orders are shipped
- Build a calendar view for scheduling appointments
How to Submit a Great Feature Request
Tips for getting your features built faster and better.
Start with the problem, not the solution
Tell us what you're trying to achieve or what's frustrating your users. We might have a simpler solution than what you're imagining.
Instead of:
"Add a dropdown menu with filter options"
Try:
"Customers are struggling to find products. They often know the category but get overwhelmed by the full list."
Add details after submitting
Don't stress about getting everything perfect in the initial form. Once submitted, you can click on your task to:
- Upload images - screenshots, mockups, or reference designs
- Add comments - clarify requirements or answer questions
- Attach files - PDFs, documents, or spreadsheets with data
Be specific about who and when
Help us understand the context:
- • Who will use this feature? (Staff, customers, admins?)
- • When will they use it? (Daily, occasionally, in emergencies?)
- • What happens if they can't? (Workaround? Lost sale? Frustration?)
What Isn't a Feature?
Use the right task type for faster resolution.
Bug
Something that was working is now broken, or doesn't work as intended.
"The checkout button doesn't work on mobile"
Change
Modify something that already exists - text, styling, behaviour.
"Change the 'Submit' button to say 'Place Order'"
Support
Questions, help requests, or things you're not sure about.
"How do I export the customer list to Excel?"
Why does this matter?
Using the right task type helps us prioritise correctly and resolve your request faster. Bugs get urgent attention. Support questions often have quick answers.
Frequently Asked Questions
Common questions about feature requests.
It depends on complexity. Simple features might take a few hours, complex ones could take days or weeks. Once your feature is approved and scheduled, you'll see it move through the sprint stages. We don't give time estimates upfront because they're often wrong - instead, you'll see real progress as work happens.
Yes, while your task is still pending or in the sprint queue. Just click on it and add comments or attachments with updated requirements. Once work has started, changes may require a new task to avoid scope creep and delays.
Your feature goes through these stages:
- Pending - Awaiting review and prioritisation
- Ready for Sprint - Approved and queued for development
- In Progress - Currently being built
- Completed - Ready for you to review on staging
- Approved - You've signed off, ready for production
- Live - Deployed to your production site
When a feature is completed, you'll review it on the staging site before it goes live. If something isn't right, you can reject it with notes explaining what needs to change. The task goes back for revision. That's exactly what the review process is for - nothing goes live until you approve it.
Submit each feature as a separate task. This makes it easier to track progress, prioritise work, and review completed features independently. A big list of features in one task becomes hard to manage and harder to review.
Ready to submit a feature?
Head back to your project and click the "New Feature" button to get started.
Back to Portal