Hmm. That's a template being broken, but it actually looks like the template is being fed bad data, probably by a poorly written custom field add-on. (I can say that, I've written custom field add-ons that do something similar)
I'd ask the user what filter they are running and get them to look at the columns defined for it. Then look at the field type for each column - what are all the custom field types for them? Are there any non-standard ones?
Both really. My instinct (which may well be wrong) is that you have a broken custom field. When the issue navigator is asking it for data to be displayed, it's handing back garbage which the navigator can't handle. The reason it's doing that is that the plugin that provides the custom field has a bug.
When I coded a custom field that did this, it was because I'd forgotten the null answer. I had a field which worked out some numbers based on a couple of other fields, which mostly worked, until one of those fields was empty. That gave a null as the input to my calculations, which then returned a null to the navigator, which then couldn't do "x < null" in the display. The fix, of course, was to take empty fields as having 0 values.
Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot