Remove AHA references

_data/sidebars/scos_user_sidebar.yml

@@ -104,8 +104,6 @@ entries:
       nested:
       - title: How Spryker Support works
         url: /docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
-      - title: Handling new feature requests
-        url: /docs/scos/user/intro-to-spryker/support/handling-new-feature-requests.html
       - title: Case escalation
         url: /docs/scos/user/intro-to-spryker/support/case-escalation.html
       - title: Getting support

docs/scos/dev/back-end-development/extend-spryker/development-strategies.md

@@ -56,7 +56,7 @@ In your project, you don't store prices in Spryker OS, but in an external system
 
 {% endinfo_block %}
 
-If an extension point is missing, register it in [Spryker Ideas](https://spryker.ideas.aha.io/), so we add it in future.
+If an extension point is missing, you can send a request to your Spryker account manager, and we will add it in future.
 
 Spryker OS support: High, you can safely take minor and patch releases.
 
@@ -80,7 +80,7 @@ When specific OOTB Spryker behavior doesn't fit Project requirements, you can en
 
 {% info_block infoBox "Let us know which extension point is missing, so we can add it in the core" %}
 
-Register missing extension points in [Aha ideas](https://spryker.ideas.aha.io/).
+If an extension point is missing, send a request to your Spryker account manager, and we will add it in future.
 
 {% endinfo_block %}
 

docs/scos/dev/drafts-dev/roadmap.md

@@ -27,8 +27,6 @@ redirect_from:
 **Updated: April 2021**
 We at Spryker are happy to share our plans with you. The plans below are guidelines that give us direction  to continuously evolve and improve our product. However, we are also flexible, and we constantly listen and adapt. Therefore, our plans could change. So although we are good at fulfilling our commitments, we reserve the right to change our priorities, remove or add new features from time to time. If you are planning anything strategic based on this list, you might want to talk to us first, either by contacting your Spryker representative or one of our [Solution Partners](https://spryker.com/solution-partners/).
 
-If you see a feature that you like, [create an idea in our Aha](https://spryker.ideas.aha.io/ideas/) and let us know why the feature is important to you.
-
 {% info_block warningBox %}
 
 The roadmap contains features and not architectural items, enhancements, technology updates, or any other strategic releases we are working on. We kindly ask you not to base any business decisions on these lists without consulting with us first.

docs/scos/dev/guidelines/project-development-guidelines.md

@@ -56,7 +56,7 @@ For example, customize the names by adding the project name.
 
 ## Avoid using, extending, and overriding Private API
 
-Instead of using, extending, and overriding [Private API](/docs/scos/dev/architecture/module-api/declaration-of-module-apis-public-and-private.html), register the missing extension points in [Spryker ideas](https://spryker.ideas.aha.io/). In future, we will add the registered extension points, and you will be able to extend it via Public API.
+Instead of using, extending, and overriding [Private API](/docs/scos/dev/architecture/module-api/declaration-of-module-apis-public-and-private.html), send a request about the missing endpoints to your Spryker account manager. In future, we will add the extension points, and you will be able to extend it via Public API.
 
 
 ## Keep modules up to date

docs/scos/user/intro-to-spryker/support/getting-support.md

@@ -21,14 +21,15 @@ redirect_from:
   - /v1/docs/en/getting-support
   - /v6/docs/getting-support
   - /v6/docs/en/getting-support
+  - /docs/scos/user/intro-to-spryker/support/handling-new-feature-requests.html
 related:
   - title: How to use the Support Portal
     link: docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html
   - title: How Spryker Support works
     link: docs/scos/user/intro-to-spryker/support/how-spryker-support-works.html
   - title: How to get the most out of Spryker Support
     link: docs/scos/user/intro-to-spryker/support/how-to-get-the-most-out-of-spryker-support.html
-  
+
 ---
 
 If you need technical help for issues that can't be resolved with our documentation, you can always count on our support team.

docs/scos/user/intro-to-spryker/support/handling-security-issues.md

@@ -28,7 +28,7 @@ If you find a security issue in a Spryker product, please report it to us.
 
 ## Reporting a security issue
 
-Do not use public AHA Ideas, public Slack channels, or other public channels to report a security issue. Instead, send an e-mail to [security@spryker.com](mailto:security@spryker.com) in English and include system configuration details, reproduction steps, and received results. Your email will be forwarded to our internal team and we will confirm that we received your email and ask for more details if needed.
+Do not use public Slack channels or other public channels to report a security issue. Instead, send an e-mail to [security@spryker.com](mailto:security@spryker.com) in English and include system configuration details, reproduction steps, and received results. Your email will be forwarded to our internal team and we will confirm that we received your email and ask for more details if needed.
 
 ## How we are handling security reports