nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Resolution field in JPD project is still unresolved when Ideas are set to the Done status

Yong Yang

Hi guys,

I found the resolution field is still Unresolved after the status is Done. I could search it out with JQL statuscategory = Done, which is quite different from that in JSW. Is it a bug or not?

It seems that JPD project is a team-managed project. Is the Resolution field abandoned in this kind of project? If so, it's better not to be shown in the issue list.

Thanks,

Yong

Accepted answers

Tanguy Crusson

Hi @Yong Yang what would you use "resolution" for, for an idea?

All comments

Tanguy Crusson

Hi @Yong Yang what would you use "resolution" for, for an idea?

Jan-Hendrik Spieth

@Tanguy Crussonmy 50 cents:

For starters, we want resolution to be consistent across all our issue types.

And about a use: we just have one Done state, both for cancelled/killed/stopped issues, as well as things that we did successfully. So we have two resolutions, "Resolved" and "Unresolved" (the names don't matter, the meaning does).

Yong Yang

Hi @Tanguy Crusson

Keep consistent across all Jira family products.

We have two gadgets in the system dashboard for all guys:

1.Unresolved Issues (including ideas) => JQL: resolution = unresolved

2.Resovled Issues => JQL: resolution != unresolved

If we don't use the resolution field in JPD, then we have to write all the related statuses in the JQL, which will be a bit complicated or unreadable.

Please consider this requirement and add to JPD. We may implement it in the workflow automation rule to add the resolution field in the post function. Thanks,

YY哥

michael_thurm

Hi, i agree with the others. Resolutions are helpfull also for statistics/metrics.
E.g. Time in Status for an Idea (which is only calculated after the resolution is set to resolved).

for us it would be very helpfull to
- measure how long an idea is in each status before getting resolved
- how many ideas get resolved vs. new created (one of the most important metrics for us to discuss need of more resources) - this works perfect in jira with the Dashboard-Charts but because of the missing resolution we cant do it on Discovery

@Tanguy Crusson

Matt Hadfield

Hi @Gary Spross , I am trying to implement a similar automation. I am getting the same error about the resolution field not being available but from what I can see I am using the Edit action the same way as yourself. Any ideas?
Screenshot 2025-07-31 100916.png

Gary Spross

Can you share a screen capture of your rule details as well as a screen capture of the audit log showing a failed attempt?

Matt Hadfield

Thanks for the repy Gary but we went in a different direction in the end.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-product-discovery