Skip to content

Instantly share code, notes, and snippets.

@gengwg

gengwg/jira-idea-project.md

Created October 11, 2025 18:02
Show Gist options
  • Save gengwg/61179b790baa881053758cd242c1d91b to your computer and use it in GitHub Desktop.
Save gengwg/61179b790baa881053758cd242c1d91b to your computer and use it in GitHub Desktop.
Download ZIP
Raw
jira-idea-project.md

In Jira, an "idea" is not part of the standard project hierarchy (Project > Epic > Story/Task) but is a separate concept used for early-stage innovation and is managed in a dedicated tool called Jira Product Discovery (JPD). Ideas are for capturing and prioritizing potential work before it becomes part of the development backlog.

Here is a comparison of how ideas fit into the overall workflow:

Aspect Jira Product Discovery (The "Idea" Space) Jira Software (The "Development" Space)
Purpose Capture, discuss, and prioritize opportunities and solutions. Plan, track, and execute development work.
Unit of Work Idea. Issue (e.g., Epic, Story, Task, Bug).
Primary Goal Decide what to build. Build and deliver the selected items.
Connection Promising ideas are sent to Jira Software as Epics or Stories. Epics and Stories from JPD are broken down and worked on.

💡 How to Work with Ideas in Jira Product Discovery

Jira Product Discovery serves as a central repository for product ideas and preliminary concepts. Teams can collect feedback, enrich ideas with data, and prioritize them using built-in scoring methods before deciding what moves into development.

When your team decides an idea is valuable to pursue, you can send it to Jira Software for execution. In Jira Product Discovery, you can convert an idea into a Jira Epic or link it to an existing Jira issue. This creates a clear traceability link from the initial concept to the actual development work.

🗺️ Putting It All Together: The Complete Workflow

The overall innovation-to-delivery process in the Atlassian ecosystem looks like this:

  1. Ideation & Discovery (Jira Product Discovery): Collect raw suggestions and feedback. Group and refine them into coherent Ideas. Prioritize using strategic goals and data.
  2. Prioritization & Decision (Jira Product Discovery): Use visual tools and scoring to decide which Ideas to act on.
  3. Execution (Jira Software): Selected Ideas are sent to a Jira Software project, typically as an Epic or Story. The development team breaks them down into Tasks and Sub-tasks and works on them.
  4. Delivery: The team completes the development work, and the feature is delivered to users.

This workflow ensures a structured process from initial suggestion to final product increment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment