Nested Bundled field not displaying correctly

[Eric R Hartway]

Hello.  I'm editing a request type for the Jira Service Desk portal. I have two custom fields, one is a "Deviniti [Extension] - Bundled Field" and the other a "Deviniti [Dynamic Forms] - Dynamic Select".  I've nested the bundled field in the dynamic select for it to display if the customer selects "Yes" to the top level question.  The issue I'm seeing is with the layout of the nested bundled field.  When the layout is horizontal, the bundled fields all show on top of each other rather than side by side (this only happens when the bundled field is nested).  I've tested all the layout settings, and the only "fix" I've found is to set the layout to vertical, which is not desired by my stakeholders.  Any help fixing his would be much appreciated.  See print screens for more details.

Here is what it looks like when a customer selects "yes"

And here is how it should look:

[Stefan Vahlgren]

Hi again.

I have had a mail correspondence with Arsenale Support team and here comes a summary.

I had to do a JIRA reindex in order to get the chart in the correct way. After the reindex, recreate the Current Issues Value report again in the gadget, and then push the blue "Run Report" button from the report Configuration page. The chart is showing one bar for each unique Parent Test value that the Search critera in the report gives. The bars are showing correct height with correct colors mapped to the Statuses. After the reindex the chart stays correctly and gets updated when for example more issues are added (which is found by the report Search critera), without another reindex.

A side note to this is that it is not functional to use ORDER BY in the search critera, since this report will order the bars according to the number of issues in the bar. Since I want to show trends over time, I need to order the bars by for example Created Date field. Arsenale is saying that support for more customizable ordering which would enable this is probably added in an upcoming release.

[Stefan Vahlgren]

Thanks for the extensive description. I'm almost there now, but the chart is'nt showing correctly. I followied your description exactly. I have got the Parent Test field as a column in the answer of the jql, like this:

Status Key(Child) Parent Test
Failed AUTO-131 AUTO-127
Passed AUTO-129 AUTO-127
Failed AUTO-126 AUTO-122
Passed AUTO-124 AUTO-122
Passed AUTO-119 AUTO-117
...

total of 18 hits

However, my chart looks like this:

For segment by I am using Status field, and for Value Of I am using Parent test, like in your example above.
I expect to have multiple bars, where one of them is for the Parent Test AUTO-127 with height 2 (since there are two linked issue to that issue), coloered half blue and half red.

I have Arsenal Dataplane version 1.8

[Stefan Vahlgren]

It seeems that the picture is'nt working for some reason. Anyhow, the chart looks is just containing one bar, with height 18. At the Y axis (named Parent test) the value is "None"

[Scott Dudley [Inactive]]

Stefan,

To figure out what is going on, I would also try temporarily adding a segmentation of "Issue" to the configuration to see if the issues represented in the chart are the ones that you expect. If the issues are correct, then it looks like it might be an issue related to the JIRA indexing.

Thanks!

[Stefan Vahlgren]

Hi again.

I have had a mail correspondence with Arsenale Support team and here comes a summary.

I had to do a JIRA reindex in order to get the chart in the correct way. After the reindex, recreate the Current Issues Value report again in the gadget, and then push the blue "Run Report" button from the report Configuration page. The chart is showing one bar for each unique Parent Test value that the Search critera in the report gives. The bars are showing correct height with correct colors mapped to the Statuses. After the reindex the chart stays correctly and gets updated when for example more issues are added (which is found by the report Search critera), without another reindex.

A side note to this is that it is not functional to use ORDER BY in the search critera, since this report will order the bars according to the number of issues in the bar. Since I want to show trends over time, I need to order the bars by for example Created Date field. Arsenale is saying that support for more customizable ordering which would enable this is probably added in an upcoming release.

[Stefan Vahlgren]

Hi Scott and thanks for quick response.

The Linked issue in my case is a Jira native issue link, which is found under "Issue Links" if you view the issue. the value for Linked issues in a issue filter search is shown under column Links

So in my example in my original post, there are two issues that link to the the same issue with issue key 1

[Stefan Vahlgren]

Sorry, I forgot to answer all your questions in your answer.

So the Linked issue is what is sounds like. The issue that is linked from the issue sound in the search result.

1,2,3 is issue keys. Actually the look like STRING-1, but only wrote 1 to simplify

Status is a custom field that is set in all 4 issues in the search response, to either "Passed" or "Failed"

Date is the Created field, with value as a date when the issue was created.

[Scott Dudley [Inactive]]

Hi Stefan,

Can you explain what "Linked issue" represents in your example? Is this a custom field? A specific type of issue link to another issue (or set of issues)? Or something else?

Do the "1", "2" and "3" refer to issue types (like you suggested at one point above), or to actual issue IDs, or something else?

Also, where does the "Status" come from? I understand it is a custom field, but if you are linking issues, from which issue?

Lastly, what dates does the "Date" column represent?

If you explain where that data comes from, I will be happy to suggest how to make the appropriate fields or values available in the appropriate place in Dataplane.