The Joomla project is introducing a redesigned workflow for handling feature requests - an approach aimed at making the process more transparent, more predictable, and easier to manage for both maintainers and the wider community. This new system is currently in a trial phase, and community feedback will play a key role in refining it further.

Why a New Workflow?

Over the years, the Joomla issue tracker has accumulated a large number of feature requests with varying levels of activity and clarity. Maintainers have faced increasing challenges in evaluating, prioritizing, and communicating decisions around these ideas.

The new workflow addresses these challenges by:

• Creating a structured, predictable lifecycle for feature ideas
• Improving visibility into the status of each request
• Encouraging community participation while reducing noise
• Ensuring maintainers can focus on active, high‑value proposals

The Feature Request Flow

The new system organizes feature ideas into clearly defined stages. Each stage reflects the maturity, activity level, and decision status of a request.

1. Feature Evaluation

An open discussion space where anyone can propose new ideas.
This is the starting point for all feature requests.

2. Cold Features

Older or low‑activity ideas are moved here.
They remain visible and accessible but are not actively reviewed unless renewed interest emerges.

3. Approved Features

Ideas that maintainers have accepted for future implementation.
Each approved feature includes a target Joomla version, depending on compatibility and roadmap considerations.

4. Rejected Features

Ideas that will not move forward, with clear reasoning provided for transparency.

5. Implemented Features

Completed features that have been merged into Joomla and shipped in a release.

6. Archived Discussions

Duplicates, irrelevant topics, or discussions that no longer require active engagement.

This structure ensures that contributors can easily understand where an idea stands and what comes next.

Migrating Existing Feature Requests

To bring consistency to the backlog, all existing GitHub issues labeled Feature will be moved into the new Feature Request Discussion area.
They will be classified based on activity:

• Feature Evaluation: last comment in 2025/2026
• Cold Features: last comment before 2025

This allows maintainers to focus on current, community‑driven ideas while preserving historical proposals for reference.

Submitting a New Feature Request

Anyone can propose a new feature by opening a discussion in the Feature Evaluation category.
To ensure productive evaluation, each proposal should include:

• A clear problem statement
• A proposed solution
• The expected benefit or use case
• Optional: screenshots, mockups, or external references

This structure helps maintainers and contributors quickly understand the intent and value of the idea.

Evaluation Timeline and Community Participation

Once submitted, a feature idea enters a structured evaluation period:

• Within 2–4 weeks: Maintainers decide whether to keep the idea in evaluation or reject it (e.g., as a duplicate).
• During evaluation: The community is encouraged to comment, refine, and upvote ideas.
• Within 4–6 weeks: A final decision is made - approval or rejection.

Constructive, collaborative discussion is strongly encouraged throughout the process.

Roles and Responsibilities

The workflow clarifies who does what:

Anyone

• Submit new feature ideas
• Comment, discuss, and provide feedback

Maintainers

• Move ideas through the workflow
• Provide rationale for decisions
• Set target Joomla versions
• Close discussions once decisions are made

This balance ensures openness while maintaining direction and accountability.

Guiding Principles

The new workflow is built on a few core principles:

• Encourage broad community participation
• Maintain clear timelines for decisions
• Provide transparent reasoning for rejections
• Allow Cold Features to be revisited at any time

A More Transparent Future for Joomla Development

This new feature request workflow represents a significant step toward a more organized, collaborative, and sustainable development process. By giving contributors a clearer path to propose and refine ideas - and by giving maintainers a structured way to evaluate them - the Joomla project strengthens its commitment to open‑source excellence.

As this workflow is still in its trial phase, community feedback is essential. The Joomla team invites everyone to participate, share ideas, and help shape the future of the CMS.