JPD - Assigning Separate Stakeholder Stack Ranked Lists

[Jesse Zamazanuk]

Hey community,

We currently use Aha! for idea / feature request prioritization and Atlassian for pretty much every other part of Software development, including JSM for bug reports and "quick" admin config requests. I would really like to consolidate and move what we do on Aha into Jira Product Discovery, but I would greatly appreciate some help in finding out how to accomplish what works for us. 

In Aha, we have ideas / requests that are submitted via form with some basic custom fields that capture perceived impact (1-5), company objectives supported (multi-select), and department (which is the functional organization of the business that the feature is for such as Ground Operations, Customer Experience, etc). I periodically meet with the director of each department to review requests and stack rank them. In this meeting, it's not always the most impactful tickets that come out on top - it's a combination of impact, effort, and timing that ultimately play into their stack rank. 

I then meet with a few members of the Executive team to review these stack ranks and get big-picture insight so that we can plan out our software roadmap in a way that delivers the most value to the company as a whole.

What I'm struggling with is finding a way to represent these individual stack ranks in Jira Product Discovery. Aha! has a "prioritization" view where you can drag and drop ideas and the stack rank field automatically updates accordingly. 

Any ideas? 

[Olha Yevdokymova_SaaSJet · Accepted solution]

Hi @Jesse Zamazanuk ,

It sounds like you're running a well-structured prioritization workflow—and you're right, Jira Product Discovery (JPD) doesn't yet have native support for stack-ranked prioritization by stakeholder group in the same drag-and-drop way as Aha!.

Here's how Smart Forms for Jira can help bridge the gap and even simplify parts of your current setup:

---

✅ Smart Forms for JPD Idea Collection

You can create custom Smart Forms that stakeholders fill out to submit new ideas or review and rank existing ones. These forms can be shared externally (no Jira account needed), embedded in Confluence or your intranet, or sent via email or Slack.

---

🧠 Pre-Fill JPD Fields with Form Data

Using smart value mapping, your form responses can auto-populate JPD fields like:

• Impact (1–5 scale)

• Company Objectives (multi-select field)

• Department / Stakeholder Group

• Custom Priority or Stack Rank field (optional custom field in JPD)

Once submitted, this info is structured and ready in JPD so you don’t have to manually copy data or run messy spreadsheets, so you can create ranking column by different stakeholder groups. In the form with conditional logic that can see only the field that are relevant to stakeholder group.

---

🔁 How This Supports Your Stack Ranking Process

You could:

1. Send the form before stakeholder meetings so directors can rank/review requests individually.

2. Map their department name to a custom field for easy filtering.

3. Sort and group ideas by department in a JPD view.

4. Add a “Stack Rank” number field to capture their prioritization during your meeting.

This gives you repeatable views per stakeholder group and a structured way to track their feedback without relying on multiple tools.

[Carolyn McNicoll]

Is the RICE formula the same as stack ranking?  You can set that up in JPD.

The RICE formula in Jira Product Discovery (JPD) is used to prioritize ideas based on four factors: Reach, Impact, Confidence, and Effort. It is calculated as: (Reach * Impact * Confidence) / Effort, allowing teams to evaluate and compare initiatives effectively.