You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi. I have a custom field (at Epic level) intended to capture which (1 to many) analysts are assigned to the piece of work. On the dashboard widgets, if I select this field (even using a filter for non-empty values) all I get for the field data is 'none'. The staff I've selected don't seem to be able to show anywhere... is it a bug?
Would like to see, for example, if my data is:
Then a Dashboard widget on 'Custom_user_field1' not empty could show:
Here's a pic of pie results using the real field. 7 epics, yup. 9 user values in the field across the 7 epics, yup. Pie shows... 'none'.
Hi @Jamie Bell -- Welcome to the Atlassian Community!
Is this for a team-managed or a company-managed project?
If it is team-managed, there is a known problem with People fields not working with all dashboard gadgets. You may watch/vote for that defect to see progress: https://jira.atlassian.com/browse/JRACLOUD-72205
Kind regards,
Bill
Thanks Steve. Definitely that, & yes is a Team project.
Always a concern with bugs of this kind in Jira, that they take an eternity to get recognised & resolved (almost 4 years so far for that one!) Just makes Jira that much harder a sell to decision makers over time, as it shouldn't be the case for a mature tool like this.
So I thought it best to first find out if a workaround or user error was possible... Would've been nice! Now I just have to tell key stakeholders there's no way to dashboard/report on this, & the field is therefore mostly useless, apart from as individual issue reference. Shame.
Cheers. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A possible work-around for this is...
A recent change allows team-managed projects (TMP) to share/use the custom fields created for the site and company-managed projects (CMP).
If you create a multi-select user field at the site level, it could then be used by your TMP (instead of the People field type). That may work correctly with the gadgets, as it does so for CMP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.