Why are value, effort, impact, and Impact Score fields empty outside the JPD?

[Peter Tikhomirov]

Hello everyone! I have a question.

When I create an idea in Jira Product Discovery, I can set parameters like Value, Effort, Impact, and Confidence, and the system calculates an automatic Impact Score based on them. However, the issue is that when I try to access the Impact Score field (or any of these fields) through search, automation, or third-party Jira plugins, they all appear empty.

I can see the values filled in within Product Discovery itself, but whenever I access the idea from outside (e.g., via JQL, automation rules, or external tools), these fields show up as blank.

Why does this happen? How do you deal with this kind of issue? And is there any way to solve it at all?

Thanks!

[Bill Sheboy · Accepted solution]

Hi @Peter Tikhomirov 

My understanding is those dynamic fields are implemented in JPD code, presented with the UX, and are not stored with the Idea's data.

In other community posts, I have read workarounds where:

• a non-dynamic custom field is added (e.g., number, text, etc.),
• automation rules are used to set the values based upon changes to the inputs...matching the logic used for the dynamic field,
• and then the stored custom field value may be accessed from outside of JPD, such as with JQL, etc.

Kind regards,
Bill

[Tanguy Crusson]

@bill is correct - these fields are not supported in the backend yet, they're just calculated on the frontend - hence why you can't use them in JQL, automations, etc. We have a project planned to fix that. 

[Chris Lloyd]

Hi @Tanguy Crusson

I found this thread while researching this same issue. I have found that a brand new instance of JPD created a couple of weeks ago (Dec 25) does present valid Value, Effort, Impact fields via the REST API but older JPD deployments do not. Even within a single Jira environment, JPD projects created at different times have different fields available.

Was there progress in ths project you mentioned in your comment that explains this difference in behaviour?

Many thanks!

[Tanguy Crusson]

@Chris Lloyd it should work the same for all projects 🤔

The behaviour will depend on the field type:

• Fields of type Rating, number, slider, etc. will return a valid value
• Formula fields won't return a value (they're still calculated in the front-end)

If you're seeing different values depending on the project, are you sure the fields are of the same type?