Set the TFS Iteration and Area path per feature or requirement
Having a single area path for the entire product doesn't make sense. This value will usually depend on the feature, as area paths define the area of code impacted by a work item. This helps with evaluating code churn and test coverage. It needs to...
Jonathon Leeke
about 9 years ago
in Integrations
6
Already exists
It would be helpful if one of the mapping options with Pivotal Tracker could include the following options:
Master Feature to Epic
Feature to Story
Requirement to Task
Instead, the only option for mapping to Epics in PT is to use Initiatives. Th...
Tom Beck
about 6 years ago
in Pivotal Tracker
1
Future consideration
Show comments added in JIRA as part of a state transition.
Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA.
This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
Michael Buonassisi
over 5 years ago
in Jira
2
Future consideration
The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
Wen-Wen Lin
over 5 years ago
in Jira
0
Future consideration
To help me quickly troubleshoot background job logs: Tag each Update all linked records job type with the integration name. You are already doing this with Integration Import job types. In the case where a background job has failed, you write in t...
Alfred S
over 2 years ago
in Jira
0
Future consideration
Change default visibility of ideas submitted via Slack
I recently installed the Slack integration. When one of our team members submits an idea via Slack, it shows up in our Aha dashboard but not on the associated portal page. As of right now, I believe I'd have to change the visibility of each new id...
Guest
about 6 years ago
in Ideas / Slack
0
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
over 8 years ago
in Jira
1
Future consideration
Ability to update a file attachment of a feature and update in the linked record of JIRA as well
Hi - We have Aha! - Jira integration where our features are mapped to JIRA stories. Features also have several file attachments which get propagated to JIRA stories. However, our Product Managers need to update the file attachments. Currently ther...
Michael Zadda
almost 7 years ago
in Jira
1
Future consideration
Our support team has adopted uservoice as our support platform. They're using this to collect feedback on the product. It'd be great if we could integrate this into Aha's own ideas list
Guest
about 10 years ago
in Wanted
2
Unlikely to implement
More complete field mapping between Aha! and FogBugz
Both products are feature rich and have many alignments which would be great to keep in sync.
Aha! Feature Type - FogBugz Case Category
FogBugz has an "Area" concept which doesn't map directly. At least being able to select the target area for ne...
Guest
over 9 years ago
in Integrations
4
Will not implement