When I create a custom pivot report, the entire report has a title, which is displays on notebooks. But when I export to image or PDF, the title is no longer there.
Under customize report, I would like the ability to:
add an optional title to the...
Allow Setting the Knowledgebase Homepage Meta Title
What is the challenge? The knowledgebase title is set to "Home Page" and cannot be customized. What is the impact? Vague title in the browser tab, SEO Describe your idea A field to set the title of the KB homepage
I would like to be able to publish notebooks created in aha to digital screens around our offices, this would cover customer stories, strategic roadmap and value statements to members of our internal teams. Whilst I can publish these to individual...
Fraser Mayfield
almost 9 years ago
in Presentations
1
Shipped
Support parent-child moving across workspaces and Jira projects
In the Aha! we have Features that reference a parent Epic in another workspace. In Jira we have issues that are children of an Epic in another project. This cross workspace/project relationship is supported in Aha! and Jira, but the integration do...
Michael Bruner
over 3 years ago
in Integrations
4
Shipped
Update "Related Features" Data Column to Include Status
The "Related Features" data column is valuable for creating reports that show relationships between features that may be in the same or different releases. However, typically when reviewing such a report, another critical piece of information is u...
In situations where there are large product hierarchies consisting of many product lines and many products in those product lines, it becomes important to be able to filter reports using both the Product Line Name as well as the Product Line type ...
We would like to provide in app polls/surveys for ideas to help prioritize features we work on next. Background: We have a number of shortlisted roadmap items which we have developed business cases for. As one of the inputs to prioritizing these r...
Update epic name in JIRA when feature name changes in Aha!
Currently only the issue Summary field is updated and not the Epic name. The Epic name field should also be updated to match the Summary when it changes in Aha!
Ability to "lock" a custom field, so no user can edit it
Some of our fields in Aha are solely dictated by the field in Jira, for example Status.
Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrite...