Engineering Requests¶
We value your feedback and ideas. Engineering requests help us prioritize development efforts and build the features that matter most to our customers. Use this page to understand how to submit feature requests, report bugs, and suggest enhancements for the MOJO platform.
How to Submit a Request¶
All engineering requests should be submitted via email to:
Include [Engineering Request] in the subject line so our team can route your request appropriately.
Request Types¶
Feature Requests¶
Have an idea for a new capability? We want to hear it. Feature requests help shape the MOJO roadmap.
What to include:
| Field | Description |
|---|---|
| Title | A short, descriptive name for the feature |
| Use case | What problem does this solve? How would you use this feature? |
| Current workaround | How are you handling this today, if at all? |
| Business impact | How would this feature benefit your operations? |
| Priority | How important is this to your workflow? (Nice to have / Important / Critical) |
Example Feature Request
Subject: [Engineering Request] Bulk BIOS settings import via CSV
Use case: We manage 500+ servers and need to apply different BIOS profiles based on server role. Currently we configure each profile manually.
Business impact: Would reduce our provisioning time by approximately 4 hours per deployment cycle.
Bug Reports¶
Found something that isn't working as expected? Help us fix it by providing detailed information.
What to include:
| Field | Description |
|---|---|
| Title | Brief description of the bug |
| MOJO version | Version where the bug was observed |
| Steps to reproduce | Numbered steps to consistently reproduce the issue |
| Expected behavior | What should happen |
| Actual behavior | What actually happens |
| Logs / screenshots | Attach relevant logs, error messages, or screenshots |
| Environment | OS, browser, network details, appliance type |
Example Bug Report
Subject: [Engineering Request] Firmware update fails for Dell R750 with error 409
Steps to reproduce:
- Navigate to server detail page for a Dell R750
- Select firmware bundle "Dell-2024Q4"
- Click "Apply Firmware Update"
- Observe error 409 in the task log
Expected: Firmware update completes successfully.
Actual: Task fails with HTTP 409 conflict error after 30 seconds.
Enhancement Requests¶
Have a suggestion to improve an existing feature? Enhancements help us refine the platform.
What to include:
| Field | Description |
|---|---|
| Title | Short description of the enhancement |
| Current behavior | How the feature works today |
| Proposed improvement | What you would like to see changed |
| Justification | Why this improvement is valuable |
Example Enhancement Request
Subject: [Engineering Request] Add filtering to Resource Pools list view
Current behavior: The Resource Pools page displays all pools in a flat list.
Proposed improvement: Add search/filter capabilities to quickly find pools by name, tag, or server count.
Justification: We manage 50+ resource pools and scrolling through the full list is time-consuming during daily operations.
What Happens After You Submit¶
- Acknowledgment — You will receive a confirmation that your request has been received.
- Triage — Our engineering team reviews and categorizes the request.
- Prioritization — Requests are evaluated based on customer impact, feasibility, and strategic alignment.
- Status Updates — We will keep you informed of significant progress or if we need additional details.
- Release — Accepted features and fixes are included in future MOJO releases. See our Release Notes for version updates.
Response Time
Engineering requests are reviewed on a regular cadence. While we cannot guarantee implementation timelines for feature requests, bug reports are prioritized based on severity and impact.
Best Practices for Effective Requests¶
- Be specific — The more detail you provide, the better we can understand and act on your request.
- One request per email — Submit separate emails for distinct requests to ensure proper tracking.
- Include context — Describe your environment, use case, and business impact.
- Attach evidence — Screenshots, logs, and configuration snippets help us reproduce and understand the issue.
- Follow up — If your situation changes or you have additional information, reply to the original email thread.