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

[YY Brother]

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

[Tanguy Crusson · Accepted solution]

Hi @YY Brother 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).

[YY Brother]

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 

[Gary Spross]

Adding my agreement for proper implementation of the Resolution field within JPD.

I appreciate consistency across the Atlassian apps. I also prefer to create workflows with a single "Done" categorized status and rely on the Resolution value to indicate if it was completed, canceled, etc. With this not being an option to set within the JPD projects, I've resorted to utilizing an automation rule. I'm not a fan of this method though as the user doesn't have the ability to specify the value themselves.

Here's the automation I have in place (which I just checked and it is working properly):

[YY Brother]

Thanks for sharing. Do you have any better way to update the existing wrong Resolution (unresolved) for Done category ideas?

[Gary Spross]

Create the rule I laid out above, but instead make the trigger be "Scheduled" and have it utilize the following JQL:

projectType = product_discovery AND statusCategory = Done AND resolution IS EMPTY

Then run the rule manually.

Depending on the amount of Ideas returned, you may need to run the rule several times.

If you want to be able to specify "resolution" values other than "Done", you will need to add a few more conditionals, most likely based on the "Done" categorized statuses within your JPD projects.

[YY Brother]

 I just tested one idea with an automation:

projectType = product_discovery AND statusCategory = Done 
AND resolution IS EMPTY AND key = IDEA-28

I manually triggered this automation and got an error: 

The fields set during transition aren't available. Fields ignored:

Resolution (resolution)

[Gary Spross]

You're getting that error because you're attempting to modify the field within the Transition action, but there isn't a transition screen with that field present (which you can't configure anyway because JPD doesn't support transitional screens). You need to utilize the Edit action to modify the Resolution field. You can add it before or after the Transition action.

Note: Don't forget to remove the setting of the Resolution field from the Transition action so you won't get the error anymore.

[YY Brother]

It worked perfectly. Thanks.