# How to Suggest a Feature for makeplane/plane

> Suggest a new feature for makeplane/plane by opening a GitHub issue. Use the feature request template for faster triage and proper labeling.

- Repository: [Plane/plane](https://github.com/makeplane/plane)
- Tags: how-to-guide
- Published: 2026-06-26

---

**To suggest a feature for makeplane/plane, open a GitHub issue using the Feature request template located at [`.github/ISSUE_TEMPLATE/--feature-request.yaml`](https://github.com/makeplane/plane/blob/main/.github/ISSUE_TEMPLATE/--feature-request.yaml), which automatically assigns core maintainers and applies the correct labels for triage.**

The Plane project (makeplane/plane) is an open-source project management platform that actively welcomes community-driven improvements. If you have an idea for new functionality, the repository provides a structured workflow to ensure your suggestion reaches the right maintainers. Following the official feature request process documented in the source code helps prioritize development and keeps the project roadmap transparent.

## Use the GitHub Feature Request Template

The repository includes a dedicated issue template that standardizes how feature requests are submitted and processed.

### Template Location and Structure

The feature request form is defined in [`.github/ISSUE_TEMPLATE/--feature-request.yaml`](https://github.com/makeplane/plane/blob/main/.github/ISSUE_TEMPLATE/--feature-request.yaml) on the `preview` branch. This YAML file configures GitHub's issue form interface, ensuring every submission includes consistent information and appears in the correct format for maintainers.

### Required Fields and Auto-Assignment

When you use the template, GitHub automatically configures:

- **Title**: Must start with `[feature]:` for clear identification and searchability
- **Assignees**: Defaults to `vihar` and `pushya22` (core maintainers) to ensure immediate visibility
- **Labels**: Applies `✨feature` and `plane` for automatic categorization and filtering

The form body requires two mandatory text areas:

1. **Summary**: A concise paragraph describing the proposed functionality
2. **Why should this be worked on?**: The problem statement or use-case justification

## Follow the Contribution Guidelines

Before creating an issue, examine [`CONTRIBUTING.md`](https://github.com/makeplane/plane/blob/main/CONTRIBUTING.md) in the repository root. This document outlines the complete workflow for submitting issues and pull requests to the Plane project.

Key prerequisites include:

- **Search existing issues**: Confirm your feature hasn't been requested using the "Is there an existing issue for this?" checkbox
- **Provide clear context**: Explain both the feature and its business value to users
- **Respect the code of conduct**: Maintain constructive, respectful communication per [`CODE_OF_CONDUCT.md`](https://github.com/makeplane/plane/blob/main/CODE_OF_CONDUCT.md)

## Submitting Your Feature Request

You can create the issue through two methods:

### Direct Template Link

Use this URL to automatically load the feature request template with pre-filled assignees and labels:

```text
https://github.com/makeplane/plane/issues/new?assignees=vihar,pushya22&labels=%E2%9C%A8feature,plane&template=--feature-request.yaml&title=%5Bfeature%5D%3A+

```

### Manual Navigation

1. Navigate to the **Issues** tab
2. Click **New Issue**
3. Select **Feature request** from the template options

### Example Issue Body

If drafting locally before submitting, structure your description using this markdown format:

```markdown
**Thank you for taking the time to request a feature for Plane**

- [x] I have searched the existing issues

### Summary

Provide a one‑paragraph description of the feature you’d like to see.

### Why should this be worked on?

Explain the problem or use‑case that this feature addresses. Highlight the benefits for users or for the product’s roadmap.

```

### API Submission Method

For automated submissions via the GitHub API, use this JSON payload structure:

```json
{
  "title": "[feature]: Add bulk‑edit for work items",
  "body": "Thank you for taking the time to request a feature for Plane\n\n- [x] I have searched the existing issues\n\n### Summary\nAllow users to select multiple work items and edit common fields (status, assignee, tags) in one operation.\n\n### Why should this be worked on?\nBulk editing reduces repetitive UI interactions, improving productivity for teams handling many tasks at once."

}

```

## What Happens After Submission

After you submit the issue, the system immediately applies the `✨feature` and `plane` labels and assigns the request to `vihar` and `pushya22`. The maintainers review the proposal for technical feasibility and alignment with the project roadmap. They may request additional details or clarification through comments. Accepted features may be implemented by the core team or opened for community contribution via pull requests.

## Summary

- The feature request template lives at [`.github/ISSUE_TEMPLATE/--feature-request.yaml`](https://github.com/makeplane/plane/blob/main/.github/ISSUE_TEMPLATE/--feature-request.yaml) and enforces consistent formatting across all submissions
- Default assignees (`vihar`, `pushya22`) and labels (`✨feature`, `plane`) ensure proper triage without manual configuration
- Always search existing issues and consult [`CONTRIBUTING.md`](https://github.com/makeplane/plane/blob/main/CONTRIBUTING.md) before submitting to avoid duplicates
- Use the direct URL parameters to automatically load the template with correct metadata and title prefix
- The title prefix `[feature]:` is required for proper categorization in the project's issue tracker

## Frequently Asked Questions

### Where is the feature request template located in the makeplane/plane repository?

The template is stored at [`.github/ISSUE_TEMPLATE/--feature-request.yaml`](https://github.com/makeplane/plane/blob/main/.github/ISSUE_TEMPLATE/--feature-request.yaml) in the repository root. This file defines the form fields that appear when you create a new issue, including the required summary and justification sections that maintainers need to evaluate proposals.

### Who gets assigned when I submit a feature request to Plane?

GitHub automatically assigns core maintainers `vihar` and `pushya22` when you use the feature request template. This assignment ensures the right team members see your proposal immediately without requiring manual tagging or internal routing.

### Can I submit a feature request without using the template?

While technically possible, using the template at [`.github/ISSUE_TEMPLATE/--feature-request.yaml`](https://github.com/makeplane/plane/blob/main/.github/ISSUE_TEMPLATE/--feature-request.yaml) is strongly recommended. It automatically applies the `✨feature` label and ensures your submission includes the required summary and use-case justification that maintainers need for efficient triage.

### What should I include in the feature request body?

Include a clear summary paragraph describing the proposed functionality and a detailed explanation of why it should be worked on. Reference the specific problem it solves or the use case it enables, following the two-section structure defined in the template's text areas.