Suppress Custom Status in Report Chart Key

[PatrickHa18]

Does anyone know of any way to suppress all the custom statuses that equate with a default status in the key of a report. Maybe another. way to say this would be is there a way to create a custom label for a group in the key of a report.  For example I have report that is grouped by status and on the chart the key identifies which color represents each status grouping. However, there are several other custom statuses that my group doesn't even use that show up in the label of each group in that key, i.e. the "In Progress" group says something like "In Progress, BDR Qualified, Approved to Bid . . . ." Any ideas on how to change the label of this group in the key of the report?

[KellieGardner · Accepted solution]

If you are filtering out the objects on your report that don't apply to your group, then they shouldn't show on your chart. 

You can try changing the grouping to "status equate with" but I think you'd have to do it with text mode, which won't work for charts, so I would try to filter out those other objects that don't apply so they aren't showing. 

[PatrickHa18]

@KellieGardner - thanks for the reply. I think you are correct about the "status equates with" we had the same idea and couldn't get that to work. As for your idea about filtering out the objects (assuming you meant statuses) - the issues isn't necessarily going to be solved by filtering in or out. Thats because the issue is about how our statuses are bundled in groups in our instance and how the keys in charts display this, i.e. we have several custom statuses that equate with "In Progress" and when I show the "In Progress" group in a chart the label in the chart for that group shows all the custom statuses as well. My question may not have been written clear enough to make this apparent. In any event I am actually working at Adobe in their own instance and the sys admins have told me this is a limitation and that product team is looking to remedy maybe sometime. Thanks again for your help. 

[kautuk_sahni]

@PatrickHa18 just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

[PatrickHa18]

@kautuk_sahni - thanks for checking in - see my reply above. I hadn't marked it as accepted because it wasn't the right answer, but knowing what I know now makes sense to share here.