Reporting on Issues Converted

[BillGa]

Hi There: I am creating a report that shows issues converted to projects or tasks by our company division classifications. I've got the report to show me number of issues converted grouped by that company division but I would also like to add a sub-grouping by resolving issue type (project or task). But while I can find that field in the Columns section of the report builder, it is not available in the Groupings section. Any ideas?
Thanks very much. Bill Gattinger Mobile 780-717-6209 If you have received this email in error, please let me know by return email so I can make sure it doesn't happen again. Because emails can contain confidential and privileged material, I'd ask for your help by deleting it and any attachments. Thanks! We like to keep people up to date with information about new products and services at ATB or changes that could affect you. You can check out more about ATB and CASL at "http://www.atb.com/important-information/privacy-security/Pages/ATB-and-CASL.aspx" http://www.atb.com/important-information/privacy-security/Pages/ATB-and-CASL.aspx If you would like to unsubscribe from our updates, please use this URL - "http://www.atb.com/important-information/privacy-security/Pages/unsubscribe.aspx" http://www.atb.com/important-information/privacy-security/Pages/unsubscribe.aspx

[SkyeHa]

you could use a calculated field to read off that value and then group using that. I mean, you would have to put it on every single issue, but if you're OK with that it's a quick fix. -skye

[JohnSe1]

Thats a great answer Skye - I believe Bill should be able to add that calculated field under a header bar on the form and only have it visable to a higher access level. As that way it won't display on the day to day request screens.... that is as long as thats the desired outcome.... JohnSeitz ESPN John.W.Seitz@disney.com

[EXP_-_DustinMa]

Hi Bill, Skye and John are spot on. The reason you can't do this in the GUI (or even text mode) is because of the database relationship. A task or project can resolve multiple objects, giving it a 1:n relationship. A calculated field would always be a 1:1 relationship, which is why it works as a workaround. I hope this helps explain what's going on from the back end! Thanks, Dustin Martin Assigned Support Engineer Workfront

[BillGa]

Thanks for the great solutions and the rationale team! Much appreciated. Bill Gattinger ATB Financial