A lot of project management tools have bad road maps. Investigate those with bad road maps and attempt to integrate with the platform.
There should be two options. Use the entire project as a road map or select one task and use the subtasks as a road map.
I suggest you start with Wrike as their roadmap is bad.
Agree with the prior comments. We have multiple planning and collaboration based tools. We will consolidate and are evaluating Wrike and Aha!. If this integration was already in place the decision would be much easier.
This is a really needed integration. I get that Aha! has it's won tools for other parts of businesses, like development and marketing, but not all business use one tool, and we really need an integration with Wrike as soon as possible.
Hi, just adding my support for this feature as this post hasn't seen much attention. Our engineering team uses to Wrike for project management and the Product team uses Aha! for new features and roadmap planning. It would be great if I had the option of linking a few folders in Wrike to the features in Aha! rather than have one person work with two tools to maintain consistency.
Has anyone looked into creating a generic webhook into Wrike? We have this same scenario where we have our UX team working their 'board' in Wrike but the general flow of a Feature is captured in Aha and finishes in Azure Devops. Would be nice to get updates from Wrike regarding the progress of the feature. We also have our Marketing team handling some of the generic project management type items that also overlap with some of the functionality of Aha, specifically the product related activities. Rather than have one person work in two tools we would like to see the two systems integrated to send over the content that is related to the product.
Hi, my +1 here is for different reasons: I think most of the other tools out there that you guys integrate with do not handle the concept of "product planning" well at all. They tend to, like Jira, fall back on a doc-based approach with things like Confluence or Google Sheets to set up outlines, notes, etc. that become requirements and so on. You guys have taken that format and made into actionable items at the core of your product, which can then be moved to actual development and assignable tasks.
One thing that Wrike does well, and why I am voting for both it and another Tool that is similar, Clubhouse, is have a flexible hierarchy of tasks. Unlike Asana or Jira which you currently integrate with, Wrike has the ability to categorize tasks in actionable "Projects," so initiatives with a start and end, as well as "folders' which are similar, but are non-ending folders for tasks, similar to Products in a sense with you guys. Asana and Jira do not have this ability to group tasks into multiple types of containers that are treated differently. For this reason I have gravitated to Wrike with my on boarding to Aha, after using Wrike for some time and later giving it up due to other limitations.
For what it's worth, Clubhouse also gives you a "multi-dimensional" approach as unlike many of the other issue trackers, including Jira, Epics collect tasks out of Projects, but are not forced into a project, and are not another type of issue.
I am in fact investigating a three-way set up with Aha, Clubhouse, and Wrike which I plan to set up with my own engineering and probably unito.io or tray.io amongst the integrator suites out there, as these two have more robust multi-syncing capabilities.
Cannot wait for you guys to natively integrate with both of these tools!