Versions Compared

Old Version 16

changes.mady.by.user Govind Drolia

Saved on

compared with

New Version 17

changes.mady.by.user Manisha Khilaare

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The intent for 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

Feature Requests and Roadmap

Bugs and Defects

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

(outdated > will be updated shortly)

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:

  1. New idea (needs review): New idea submitted by customers : A customer has submitted a new idea. It is pending review by the Zephyr Enterprise Product Teamteam.

    1. 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.

    2. Duplicate idea: There is a duplicate idea that has already been entered into the system.

  2. 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.

  3. Up Next / Considering: This idea has been promoted and is under consideration for the next releases.

  4. In Design & Development: The idea is being designed/implemented and will be delivered within the next releases.

  5. Coming in the next release: This idea will be available in the next release of Zephyr Enterprise.

  6. 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.

How we select features

  1. Accepted for Discussion: The PO has reviewed the idea and decided to discuss its implementation with R&D.

  2. Selected for Development: The PO has discussed the idea with R&D. They made a decision to implement it.

  3. Postponed: The PO has reviewed the idea but postponed it for future implementation. No discussion is required at the moment.

  4. Implemented: The idea has been implemented.

  5. Deferred to Support: The idea has been marked as a defect and sent to the Support team for further process.

  6. 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:

  1. Most voted features from our Ideas Portal Feature Request Community page

  2. Features aligned to our roadmap themes: Automation, BDD support, and Quality Intelligence (Reporting)

  3. Special needs of our customers