It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
Guest
about 8 years ago
in Integrations / Jira
16
Future consideration
Sync story points to Jira without Capacity Planning
My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira.
Currently this is only accomplishable when you have enabled capacity planning, which causes me...
Michael Clinton
almost 9 years ago
in Jira
1
Future consideration
Need to support the Jira code markup option.
If the developer enters sample code as part of the description in Jira, the description gets updated in Aha!
However the code markup is translated into very large tables in Aha!
At some point, Aha! upda...
Guest
about 9 years ago
in Jira
2
Future consideration
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
Danny Archer
over 9 years ago
in Jira
17
Future consideration