Expand capabilities of editor / customize CSS for Notes
I find that the default style for notes created in Aha! make the content quite difficult to digest. For example, not being able to set the line height means that paragraph can be quie difficult to read (I think that default line height is 18px). I...
JP Guyon
almost 4 years ago
in Notes
0
Future consideration
Ability to add context to to-do e-mail reminders - for ex: Initiative Name - to-do; Release Name - to-do
Aha! sends out the "consolidated" to-do notifications in e-mails which is a nice functionality. However, as the number of to-dos increase from various goals, initiatives, releases the confusion increases as to which context these are related to. F...
Ability to add specific field from elements like feature (currently only defaults to feature name for example)
When adding other entities like scenarios to a feature, it is useful if we can associate a feature number rather than the feature name which is the default field when you use the many to many table
Arun Kalyanaraman
over 7 years ago
in Features
1
Already exists
Don't change case of customized terms in Terminology
As a Product Manager, I want terms to be displayed a certain way so that it communicates my intent. Instead of "feature", I prefer the "PBI" and "Product Backlog Item". My terms, however, get as "Pbi" and "Product backlog item", respectively. I th...
We understand that the IDs in AHA and JIRA are meant to be treated as separate IDs without a true association between the two systems. However our workflow allows us to use the same IDs in both systems, assuming we enter them in the same order. Ho...
Guest
over 7 years ago
in Jira
0
Unlikely to implement
Dynamic Filters When Using a Custom "Workspaces field" to Filter
When using filters in Features, Releases, or Roadmaps, dynamically show options that are relevant to what has been filtered. This is already implemented when using a workspaces filter and a specific workspace or group of workspaces is selected. Th...
Jeffrey Ma
almost 4 years ago
in Roadmaps
0
Future consideration
Our workflow for UX designers is that we open TODO for them on a feature, and they attach UX assets to the TODO and not to the feature (to allow PMs to review before adding to the Feature which causes them to sync to Azure DevOps). It would be nic...
Tomer
almost 4 years ago
in Features
0
Future consideration