Would like to track when a feature was sent to JIRA and by who? Can you please let me know how I can accomplish this? JIRA_KEY (I am able to pull) JIRA_KEY_CREATE_DATE (Not known) JIRA_KEY_CREATED_BY Thank you //Need this for SOC compliance//

What is the challenge? When I create an idea via the Slack integration, I'm not automatically added as a voter. When I go to check "My votes" in the portal, my idea does not show up there. This behavior is different than when I create an idea in-a...

As features are being updated in Rally by development team, a feature can get deleted in Rally for a variety of reasons. When this occurs, the corresponding feature in Aha does not get deleted automatically. Instead it remains in Aha without any i...

We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...

It would be great if we could see the description of the idea when posting it through slack (or Workplace). Additionally, if we could vote through the thumbnail/preview, that would be awesome (not sure if this is possible though). Thanks!

We implemented the sprint field mapping and have found that the sync isn't quite automatic. When we rename a sprint in JIRA - that shows up as a new sprint value along with the old one. This happens a lot and currently we run into a lot of confus...

When embedding an Aha! view that allows drilldown in Confluence, the popout boxes for the drilldowns are relatively small and make it difficult to view all of the content. The same popouts in a webpage or fullscreen view have a lot more room and m...

For users sending an idea or feature to Aha! from Slack it would be helpful to be able to optionally include a description from Slack instead of having to open Aha! to add it. The button link that opens the idea or feature is nice, but the ability...

Currently, integration fields like "Rally formatted_id" cannot be used within a formula for report calculated fields. This is limiting since it means we need to create a custom field to be based on these fields to use within the formulas. Consider...

It is almost solves the whole bunch of tasks about integration with google drive and docs in an easy, useful and competitive manner.