Feature Requests is a roadmap shared by every DiveOps centre. Ask for something you'd like the product to do, and follow it from "Requested" through to "Completed".
When you'd use this
- You want DiveOps to add or change something.
- You want to see what other centres have asked for and what's already planned or completed.
Where to find it
- Feature Requests in the dashboard menu (the lightbulb).
What the board is
- One board, shared across all DiveOps centres - not just yours. It reads like a public roadmap.
- Four columns: Backlog, Planned, In progress and Completed. Completed shows the latest 12 and a Show all button.
- Newest first. There are no upvotes.
- Requests are anonymous - other centres never see who asked.
How to request a feature
- Open Feature Requests and press Request a feature.
- Fill in Feature (a short title) and, if it helps, Details (optional).
- Press Submit request.
Who can submit: anyone whose access level includes Request features. If you don't see the Request a feature button, ask your owner or manager to check your access level in Team.
What happens next
- Your request starts as Pending approval - only you and the DiveOps team can see it. The card shows a Pending approval pill while it waits.
- DiveOps reviews it, tidies the wording (and takes out any centre name) and publishes it so every centre can see it.
- Once it's on the board you can follow its status badge. When there's news, an Update note box appears on the card explaining the status and - once it ships - how to use the new feature.
What the statuses mean
- Backlog - a good idea we have logged, not scheduled yet.
- Planned - on the roadmap to build.
- In progress - being built now.
- Completed - live; the Update note tells you how to use it. The card shows the date it was completed.
- Not planned - we have decided against it, or it was delivered in a different form. The Update note explains why. Only DiveOps sees this list.
Tips
- One idea per request - it's easier to track and discuss.
- Say what you're trying to achieve, not just the feature, so DiveOps can find the best way to solve it.
- For a bug or a private question, use Support instead - that thread stays between you and DiveOps.