Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6166 Ideas

    bhavik.shah
    bhavik.shahContributor ⭐️⭐️⭐️

    Reason added to CTA Type : All, should appear in individual CTA's reason list tooNew Idea

    Problem Description:Cannot have the exact same name CTA reason made available for more than one (but not for all) CTA Types.Example: I want “Mergers & Acquisitions” to be added as a Reason for 3 out of 5 CTA Types. Currently this is not possible because I will need to add that to each of the 3 individual CTA Types, but this does not allow me to add the exact same reason. So, I have to do this as a workaround:Add a Reason for CTA 1 = Mergers & AcquisitionsAdd a Reason for CTA 2 = Merger & AcquisitionAdd a Reason for CTA 3 = M&A Requirement:When we add CTA reasons under the “CTA Type: All”, it should list those CTA Reason and make them available for all particular CTA’s. When a CTA is selected in the “CTA Type” drop-down under the Cockpit Configurations, the one’s added under All should also be listed along with their specific Reasons.These CTA reasons should be by default activated for all CTA Types, however, an admin should be allowed to either keep those CTA reasons Activated / Deactivated for individual CTA (even though they are added for All CTA type)Note: CTA Reasons added under All should not be allowed to rename or deleted if “CTA Type” does not have “All” selected. Example:CTA = AllReason 1 - Active Reason 2 - Active  Reason 3 - Active Reason 4 - Active Reason 5 - Active Reason 6 - Active Reason 7 - DeactivatedCTA = Early WarningReason 1 - Active Reason 2 - Active  Reason 3 - Deactivated (only for Early Warning) Reason 4 - Active Reason 5 - Deactivated (only for Early Warning) Reason 6 - Active Reason 7 - Deactivated (for all CTA types) Reason 8 - Active (only for Early Warning)CTA - ChurnReason 1 - Active Reason 2 - Deactivated (only for Churn) Reason 3 - Active Reason 4 - Active Reason 5 - Active Reason 6 - Active Reason 7 - Deactivated (for all CTA types) Reason 9 - Active (only for Curn)CTA - AdoptionReason 1 - Deactivated (only for Adoption) Reason 2 - Active  Reason 3 - Active Reason 4 - Active Reason 5 - Active Reason 6 - Active Reason 7 - Deactivated (for all CTA types) Reason 10 - Active (only for Adoption)

    Blastoise186
    Blastoise186Helper ⭐️⭐️⭐️

    Add a new "Bug" topic type for bug reportsOpen

    Evening!This is a bit of an unusual idea that I’ve actually hinted at a few times in recent weeks (including under my alias on a certain webinar), but I’ve decided that I want to submit this idea properly.One of my heaviest use cases with inSided overall, is making use of the Community features to submit bug reports in a way that’s a bit more open and transparent, allows the use of integrations like Jira but also doesn’t result in me creating a huge number of support tickets that can’t be resolved without escalations anyway. It’s also less pressure on the support team at my home base, since I’d otherwise be flooding them a bit too often. Forums work great for this.However, there can be a bit of a snag. Bug reports definitely aren’t “Ideas” as such, they’re not general discussions and they’re not really suitable to be Questions, because it can clog up the unsolved questions list - especially if a power user such as myself creates a high volume of them.It would be really nice for there to be an option of a “Bug” topic type, that can be used to help distinguish actual questions or problems where someone needs help, from threads where a user is simply letting you know they broke your product and wanted to submit their findings. This isn’t something I’d intend to replace existing tools like Jira of course, but mainly something that just makes it easier to search, filter and sort through them. And most importantly, to help avoid the unsolved questions list from being overloaded!You could potentially do more with it in the future, but for an initial implementation, it could potentially start out as more of a cosmetic thing. :)