Reviewing Suggestions
The hardest part of measuring impact is remembering to log the work in the first place. The Suggestions queue removes that step: once you’ve connected a code repository, VEKTIS watches what you ship and proposes a dev item for the work worth measuring. Your job shrinks from “create a dev item for everything” to “approve or dismiss what’s already been drafted for you.”
You’ll find Suggestions in the main navigation once a repository is connected. If you haven’t connected one yet, see Connecting a repository — the queue stays empty until then.
What the queue shows
Section titled “What the queue shows”Each suggestion is a piece of work that shipped, waiting for your call. The header sums it up at a glance — for example “7 waiting · 4 ready to track · 2 older than 2 weeks.”
Every suggestion is sorted into one of two groups:
| Group | What it means | What approving does |
|---|---|---|
| Ready to track | VEKTIS already recognizes the code behind this work, so it can start measuring immediately. | Approve in one step — no extra input needed. |
| Needs a few details | VEKTIS can create the dev item, but needs you to pick a metric and an owner first. | Approving opens a short form to fill those in. |
Working the Ready to track group first is the fast path — those approvals are a single click and start measuring right away.
What each suggestion tells you
Section titled “What each suggestion tells you”A suggestion row shows:
- The title of the shipped work
- A type — Feature, Improvement, or Bug fix
- A “Ready” tag when VEKTIS can measure it immediately
- A link back to the original change in your repository, so you can check the details
- Which release it shipped in
- Its age — how many days it’s been waiting
Approving and dismissing
Section titled “Approving and dismissing”For each suggestion you have two choices:
- Approve — turns the suggestion into a tracked dev item. For Ready to track items this is one click and measurement begins; for Needs a few details items you’ll pick a metric and owner first. Either way, the title, type, and source link are filled in for you, and you can edit before saving — it’s a draft, not a commitment.
- Dismiss — clears work you don’t need to measure so it doesn’t come back.
When the queue is empty
Section titled “When the queue is empty”- “Connect GitHub to get suggestions here.” — No repository is connected yet. Follow Connecting a repository to start.
- “You’re all caught up.” — Nothing is waiting. VEKTIS adds a new suggestion whenever a feature, improvement, or bug fix ships to a connected repository, so check back after your next release.
Related
Section titled “Related”- Connecting a repository — set up the connection that feeds this queue
- How work is classified — why a change becomes a Feature, Improvement, or Bug fix
- Creating and Managing Dev Items — what happens after you approve a suggestion