I believe the Cisco customer community would be better served by not being shown a "Terminated" status for defects that are judged by Cisco Engineering to actually be enhancement requests and subsequently closed. "Terminated" is something of a customer-facing catch-all status that does not fit every closed bug it catches.
A long-winded, rambling background... After a customer runs into an issue and opens a TAC case with the Cisco Customer Experience (CX) org, the CX engineer troubleshoots and searches the CDETS (Cisco Defect and Enhancement Tracking System) for similar anomalous behaviors. If CX finds no similar CDETS ID for the customer issue, and believes the customer's hardware/software configurations are correct, they can open a new CDETS bug and link the customer's case to it.
Cisco Engineering will assign a DE (Development Engineer) to analyze the new CDETS ID who then assigns it an appropriate Severity (impact to customer network) and Priority (relative importance to fixing the bug). Sometimes the DE determines that the anomalous behavior observed by the customer is actually intended by design, which makes the "bug" a "feature". This feature behavior may not be ideal, but if it is working as originally designed, then the SEV assigned to the CDETS ID becomes "6 Enhancement". A SEV of 6 is the Kiss of Death from a bug-fix perspective, as that CDETS is no longer considered a defect.
Despite CDETS having "Enhancement" in its acronym, it was never my experience that Cisco Product Marketing ever relied on it to track enhancement requests. The Product Managers (PMs) from Business Unit (BU) Marketing used other tools to track enhancement requests, tools with fields that allowed them to enter data such as descriptions of the requested behavior, which customers are asking for the request, timeline for delivery of the enhancement, projected incremental revenue from the enhancement by fiscal year, etc. Some PMs used spreadsheets, while others used actual databases. Eventually the Aha system became the standard for the SP/Web-Scale/IOS-XR BU to manage enhancement requests and it was being rolled-out across all BUs when I retired in early 2023. Aha was to become the the unified repository for all enhancement requests across BUs and PMs would use it to rank requests in their negotiation with the Engineering when it came to submitting their priorities for implementation. Priorities were driven chiefly by their potential impact on future business. I assume Aha continued in this role after I left, but I cannot say with certainty.
Cisco System Engineers (SEs) from Sales, along with PMs, are the primary initiators of enhancement requests, not TAC engineers who cannot make any claims about future revenue. Aha is an open systems in that the SEs from other accounts can see all the requests and up-vote them to add their own voices to their implementations. If you want to drive an enhancement from concept to delivery, it typically takes your SE team to do it. SEs enter the information about the request into an Aha idea and then lobby other SEs, their own SE management chain, and the customer's Cisco Account Manager (AM) to push the product's PM and the PM's management chain to prioritize implementing the request. Since Engineering resources are limited, it is something of a Hunger Games contest internal to Cisco to determine which enhancement requests make it into each release, so it is essential to make a strong business case directly to your SE (or indirectly through your VAR). Your SE, in turn, can then make a strong case to the PMs when they consider which Aha ideas to prioritize to Engineering for the next available release that is open for new feature commits.
All the above to say: a CDETS ID being moved by some process into Aha does not necessarily get it any closer to being implemented, as Aha ideas need PM or SE champions to eventually get delivered. Reach out to your SE team to have them find the request in Aha and ask them to push for committing its delivery into a release.
Disclaimers: I am long in CSCO. Bad answers are my own fault as they are not AI generated.
