Column to Display Assignee of Child based on Max Value Points

[Georg Bauser]

Hello,

I am a newbie in Community and struggling with the following challenge:

I managed to get the max value points of items of "Type_B" onto the top level of this structure (using max#subtree {condition}). But I am struggling with getting the assignee (or any other field) into the top line, that is assigned to a descendant item of "Type_B" with the highest value points (20 in the example).
The example is a bit simplified as there are more levels with parent child links possible in my "real" challenge. 

Any suggestions how to takle this. My appreciations in advance!
Georg

[Andy Heinzer]

The Open issues filter is a default filter in Jira Cloud.   By default it has the JQL search of

resolution = Unresolved order by priority DESC,updated DESC

In this case, it's only showing issues that have a resolution field that is empty or has the value called unresolved.    (Unresolved is a special value for this system field, the field itself is typically empty or null, but when that happens Jira will show the value as Unresolved )

I would be interested to see what the resolution values are for your issues.  If they have any other value they would not be expected to be returned by the JQL filter.  Usually when I see this it happens because someone has modified the field configuration and in turn made the resolution field required.  When you do this, it forces you to enter a value on that field at all times throughout the life of the issue.   Out of the box that system field is not required.  But when you make it required, it means you have to put some value in that field even when creating issues.

[Deleted user]

Here I actually did the opposite: hid Resolution field from all screens as we are not using it ever. Can I check is there a value for an issue's resolution field without changing field configuration?

[Andy Heinzer]

Perhaps you could make a REST call in order to see other issue fields such as resolution.   Perhaps you can make a call to the /rest/api/3/issue/{issueIdOrKey} endpoint to see if that information exists.

However if you have not used REST before with Jira, it might just be easier to temporarily add that field back to the screen in question to see what value exists there.