Compatibility with Rich Filters for Jira
Hi there,
I’ve asked Rich Filters for JIra dashboard plugin
authors to support Tree Custom Field
Their reply was following
Unfortunately we’re currently unable to add dynamic filtering support for this field because the field is buggy and this creates all sorts of problem. For example, the field implementation doesn’t deal correctly with options with the same name. If you select the options (on two levels) A / X and B / X in two different issues, if you add this in a native statistic gadget, you’ll see that the gadget doesn’t make the distinction between the two “X” values which do not represent the same thing (one is a sub-option of A, the other is a sub-option of B). One will overwrite the other in the statistics.
Moreover, if you now add another option named “A/X” (on one level, the option name contains “/”), the JQL is unable to make the distinction between A/X (on one level) and A/X (A on level one and X on level 2).
There are other cases like these two. In general, the field doesn’t deal correctly with name conflicts.
Is there any chance these notes can be fixed? Having support in Rich Filters for JIra Dashboard would be highly beneficial for both plugins
Cheers,
Sergei
Comments (11)
-
repo owner -
reporter Hi
Yes, I can.
But the problem is that the field needs to work correctly in the native Jira Issue Statistics gadget. Currently, at least in the test cases presented in the previous comment, it doesn’t. The field needs to work correctly in the native Jira statistics gadgets.
-
repo owner Hm. I create test issues and standard Issue statistics gadget. I don't see problem, can you provide more info or example?
-
reporter HI Yuri,
Can you share email that I can add to the ticket I have with Rich FIlters support? That will eliminate broken phone issue.
-
repo owner me@slie.ru
-
repo owner I misunderstood the problem, I'll try to figure it out
-
repo owner - attached tree-customfield-4.0.14.jar
Can you try this version?
-
reporter Let’s proceed with this version on Rich Filters Support ticket
Their support rep has all the testcases in place and understands the issue better
-
repo owner - changed status to resolved
fix
#62→ <<cset 421abcb974ab>>
-
repo owner - changed status to new
-
repo owner - changed status to closed
- Log in to comment
Hi!
What is the problem? You can use full path (“A/X”) instead partial “X“ or ID of value for exact search