My ideas: Azure DevOps Services and Server
Sort by:
Trending
Filter by:
Status
Showing 88 of 7723
1
VOTE
Allow link of a requirement to a release (sprint)
We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
0
Future consideration
51
VOTE
Configurable unit of time for Estimation field
We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps.
Our estimation process is basically as follows:
* Product Manager creates Feature in Aha
* Product Manager send ...
10
Likely to implement
28
VOTE
Allow attachments to Feature comments to be integrated to Azure DevOps
When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...
0
Future consideration
53
VOTE
Configurable destination of imported features
As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...
9
Future consideration
28
VOTE
DevOps Integration -- Support rendering of images embedded in description field
Currently when you import from Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in DevOps....
8
Future consideration
28
VOTE
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
1
Future consideration
26
VOTE
22
VOTE
Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations
With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations.
This makes scaling integrations simple as after the first setup, a user never has to add another webhook.
With Azure DevOps (TFS), ea...
1
Future consideration
3
VOTE
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
0
Future consideration
12
VOTE
DevOps Integration: Sync "Task" Workitems with Aha's "To-Dos"
Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...
1
Future consideration