| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Starting October 11, 2024 (Zephyr Enterprise 8.2), the Zephyr Enterprise documentation moved from its current location on Atlassian to a dedicated, standalone Zephyr Enterprise documentation page. Please see: https://support.smartbear.com/zephyr-enterprise/docs/en/zephyr-enterprise-product-development-process-and-roadmap.html |
The intent of this page is to provide transparency into our roadmap process for Zephyr Enterprise, including when and how we address feature requests and enhancements, and when to expect fixes for bugs and defects.
Quick Links
Our Product Development Process
This section explain explains how we prioritize and select feature requests and defects for development.
Release Cadence
Our release cadence for Zephyr Enterprise is:
Major Releases
Customer bugs
Security and performance improvements
New features and enhancements
Cadence: Approximately every month
Patch Releases
Address blocker bugs with no workaround available
Cadence: As needed
Process for Bugs and Defects
For filing bugs and defects, please first file a ticket with our support team. Our support team who will review the bug and file it internally for our development team: https://support.smartbear.com/zephyr-enterprise/message/
Process for Feature Requests and Enhancements
Filing and upvoting on feature requests
To upvote and file new feature requests, please visit our Ideas PortalFeature Request Community portal: https://zephyrenterprisecommunity.ideas.aha.io/ideassmartbear.com/t5/Zephyr-Enterprise-Feature/idb-p/ZephyrEnterpriseFeatureRequests
New ideas (feature requests & enhancements) go through the following statuses:
New idea
: A customer has submitted a new idea. It is pending review by the Zephyr Enterprise Product
Gathering Interest: The idea has been reviewed and accepted, and has been made public in the Ideas Portal to gather interest from other customers. It will be considered for future releases.
Up Next / Considering: This idea has been promoted and is under consideration for the next releases.
In Design & Development: The idea is being designed/implemented and will be delivered within the next releases.
Coming in the next release: This idea will be available in the next release of Zephyr Enterprise.
Shipped: The idea was shipped and is available for customers.
Other possible statuses:
Feature already exists:
The functionality that is being requested is already available in Zephyr.Not Aligned:
The idea is not aligned with the strategic direction for Zephyr Enterprise, and thus it will not be considered/implemented.Not enough interest:
This idea did not gather enough votes.
team.
Unclear / Needs more information:
The request in this idea is not clear and we've requested more information and/or a call to understand it.Duplicate idea:
There is a duplicate idea that has already been entered into the system.
Accepted for Discussion: The PO has reviewed the idea and decided to discuss its implementation with R&D.
Selected for Development: The PO has discussed the idea with R&D. They made a decision to implement it.
Postponed: The PO has reviewed the idea but postponed it for future implementation. No discussion is required at the moment.
Implemented: The idea has been implemented.
Deferred to Support: The idea has been marked as a defect and sent to the Support team for further process.
Community Feedback Requested: The PO has reviewed the idea and wants to get more information, votes, or comments from the community.
How we select feature request?
Our new feature development bandwidth is made up from of features in the following buckets:
Most voted features from our
Features aligned to our roadmap themes: Automation, BDD support, and Quality Intelligence (Reporting)
Special needs of our customers