> ## Documentation Index
> Fetch the complete documentation index at: https://jira.xaviercollantes.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Feature Request

> Suggest new features and improvements for Jira MCP

Have an idea for a new feature or improvement? We'd love to hear it! Feature requests help us understand what the community needs and prioritize our development efforts.

## Before suggesting

<Steps>
  <Step title="Check existing requests">
    Search [existing issues](https://github.com/xcollantes/jira-mcp/issues) with the "Enhancement" label to see if your idea has already been suggested. If it has, you can add your support and additional thoughts to the existing discussion.
  </Step>

  <Step title="Review the roadmap">
    Check if your suggestion aligns with our current development priorities or planned features.
  </Step>
</Steps>

## Submit a feature request

<Steps>
  <Step title="Open a new issue">
    [Create a new GitHub Issue](https://github.com/xcollantes/jira-mcp/issues/new) with the "Enhancement" label.
  </Step>

  <Step title="Use a descriptive title">
    Choose a clear, specific title that summarizes your suggestion, e.g., "Add
    support for bulk ticket updates" or "Implement dark mode for web interface".
  </Step>

  <Step title="Provide comprehensive details">
    ### Problem statement

    * **Current situation**: What's the problem or limitation you're facing?
    * **Impact**: How does this affect your workflow or productivity?
    * **Use case**: Provide a concrete example of when and how this feature would be used

    ### Proposed solution

    * **Description**: How should the new feature work?
    * **User experience**: What would the user interaction look like?
    * **Implementation approach**: If you have technical knowledge, suggest how this could be implemented

    ### Additional context

    * Screenshots, mockups, or diagrams if applicable
    * Any research or data supporting the need
  </Step>
</Steps>

## What makes a good feature request?

<Tip>
  **Pro tip**: Feature requests with detailed use cases, clear problem
  statements, and implementation ideas are more likely to be considered and
  implemented.
</Tip>