Adding Reporting Categories CTA Status

@cameron_wright @faust_belarmino : We dont allow adding new reporting categories to status because we determine whether a CTA is open or closed based on the reporting category. Any CTA in a status which has its reporting category as “Closed Won” or “Closed Lost” is considered complete. If we allow customizing that, we would need to add another layer of mapping to let us know whether the CTA is considered open or closed for the new reporting category.

Also, is there any reason to not add a new status vs using a new reporting category?

Thanks for the reply! We learned this the hard way… haha. We created new CTA statuses and a new CTA category. We soon realized that the reports we created for open/closed objectives weren’t adding up correctly. 

+1 to this as we’ve gone the route of creating new statuses. Reporting based on CTA status is getting difficult to digest given the vast number of options available. Since there are quite a few that could be grouped together (ex: Recycle L1, Recycle L2, etc) the thinking was that a reporting category could be the solution for cleaning up how the data is presented.

Wondering if there is any consideration being made for expanding the reporting categories here. I understand how it can become complicated, however we’ve found a use care for a neutral closing of a CTA. We have Success Plan Objectives that the CSM works on throughout the year. The CTA will be closed at the end of the year no matter what, and we find Won vs. Lost too restrictive for some goals. Using a custom status wouldn’t currently work for us because we’re using the status to show progress toward the goal (ie. new/work in progress/25% complete, 50% complete etc). We’d want to show closed objectives that were at 50%, for example. While I could use a custom field for percentages and add a Closed Neutral status, I’d still have to assign a Reporting Category and it doesn’t feel right to assign Won or Lost - it’s just closed. 

A current use case.  We sometimes close via automation for Invalid CTAs, CTAs that no longer apply (the customer lifecycle has already progressed) or when all tasks are closed and the CTA owner just never updated the CTA status.  I really don't want to create several different Closed Statuses that should only be used in automation statuses since CTA statuses can be seen in the CTA layout and the language could be misleading.  I don't want end users to start selecting a status intended for automation.  

Another Close scenario that is neither won nor lost is when we close a CTA to "merge" it.  There is no true merging of CTAs, but we allow users to combine CTAs by marking 1 with a Closed-Merged status and including details about which CTA they are tracking their work on.  Only the CTA where they are tracking there work will truly be Won or Lost.  The Merged 1 is just Closed.

So there are a few product gaps/solutions including:

1. Allow for CTA Statuses that are only available in a Rule and not visible on the CTA layout - then we could be very specific (Closed Tasks Complete, Closed Lifecycle Status, Closed Technical Issue, Closed ref Jira xx-xxx) without this cluttering up the CTA Layout view
2. Create an additional Reporting Category out of the box Closed such as Closed Other that is neither Won nor Lost and continue to keep reporting category locked down
3. Allow admins to create unique Reporting Categories for CTA Statuses, just like they can for CTA Types