Requesting a Feature or Improvement¶
All feature and improvement requests should be logged as a task in ClickUp under Trove > Bugs/Feature Requests.
The goal is to provide enough context that the development team can understand exactly what is being requested, why it matters, and who it affects - without needing to follow up for more information.
Before submitting
Check the existing task list first to avoid duplicates. Leave the ticket unassigned.
Ticket Template¶
Title¶
Keep it short and descriptive.
| Example | |
|---|---|
| Don't | "Fix the client list" |
| Do | "Update client listing to be sorted alphabetically" |
Short Summary¶
A brief "elevator pitch" of what you'd like - one or two sentences describing the functionality at a high level.
Detailed Functionality¶
A thorough description of the functionality you're requesting. Include any specific behaviours, edge cases, or constraints that should be considered.
Functionality Seen Elsewhere¶
List any other platforms, products, or examples where you've seen this functionality or something similar. This helps the dev team understand the intent and reference existing patterns.
Users This Applies To¶
Who should this affect?
- All users
- Admins only
- Staff only
- Specific role or context
Additional References¶
Include anything else that might be helpful:
- Integration contacts or documentation
- CSV templates or data samples
- Design mockups or wireframes
- Any other relevant assets or links
Attachments¶
Upload any relevant images, documents, or references directly to the ClickUp task to illustrate the requested update or improvement.
Tips for a Good Request¶
- The more context you provide, the faster it can be scoped and prioritised
- If you're unsure about implementation details, focus on the outcome you want rather than the how
- Link to any related bugs or tasks if the request is connected to existing work