Appearance
Tracking Progress
Monitor the status of your development requests from submission to production release.
The Request Board
In the portal sidebar, open My Company → Site Requests.
The main view is a board that groups your active requests into four columns:
| Column | Description |
|---|---|
| In-Review | Confirming scope, requirements, and priority with your team |
| Development | Engineering is actively building and testing the solution |
| Draft Release | Preparing a draft release or staging deploy for validation |
| Production Release | Production release is rolling out or already live |
Above the board, summary cards show your active request count, how many are in progress, how many are completed, and the average resolution time.
Each request card shows the title, a summary excerpt, its status, submitted and updated dates, a reference code, and — where the work is tracked on GitHub — a link to the issue. Click a card to open the request.
Completed and closed requests move off the board; use the History button to browse them.
Status Overview
Request Statuses
| Status | Icon | Description |
|---|---|---|
submitted | 🔵 | Received, awaiting analysis |
triage | 🟡 | Being analyzed and classified |
in-progress | 🟠 | Being implemented by the pipeline |
in-review | 🟣 | Deployed to a preview, awaiting your review |
completed | ✅ | Approved and live in production |
rejected | 🔴 | Declined — will not be implemented |
archived | ⬛ | Closed out of the active list |
Priority
Requests carry a priority of Low, Medium, or High, shown as a badge on the request's detail page.
Request Details
Click a request to open its detail page. It has three parts:
Request Details
The details card shows the status, priority, and desired-timeline badges, the request description, submitted and last-updated times, the reference code, your company, and — when the work is tracked on GitHub — the linked issue. Where the request has been analyzed, it also shows the request type and the expected version bump.
Progress
A four-step stepper shows where the request is in its lifecycle:
- Acceptance — Request submitted and awaiting initial review
- Development — Implementation in progress
- Draft Release — Changes ready for review
- Production Release — Production release in progress or live
Conversation
A comment thread between you and the development team. Comments support Markdown, and automated status updates appear in the thread alongside human replies. You can react to a comment with a thumbs-up or thumbs-down.
The detail page updates live — status changes and new comments appear without a refresh.
Notifications
The bell icon shows request updates:
- Status changes
- Comments on your requests
- Requests awaiting your review
- Deployment completions
You can tune what you receive in Account → Notification Preferences.
Taking Action
Your controls on a request are the Conversation and Archive:
Add a Comment
Use the comment box on the request's detail page to ask for status, provide additional information, or request adjustments. The team responds in the same thread.
Archive a Request
If you no longer need a request:
- Open the request (or find its card on the board)
- Click Archive request and confirm
Archived requests are hidden from the active list, become read-only, and are permanently deleted after the retention period.
Troubleshooting
Implementation Taking Too Long
Complex requests take longer. If concerned:
- Check the Progress stepper and the automation status badge
- Look for automated updates in the Conversation
- Add a comment asking for status
Unexpected Changes
If the implementation doesn't match your request, say so in the Conversation — be specific about what's wrong, and the team will iterate.
Next Steps
- Reviewing Completed Work — Review and publish
- Submitting Requests — Create new requests
- What are Dev Requests? — Learn the system