Adoption of Aha has been cumbersome because our development team uses Redmine. The integration feels woefully incomplete. The overhead of manually having to update estimations, status, comments, and syncing releases has been a stumbling block for our company as it's been difficult to get an idea where our engineering team is with the features we are sending them.
This is the missing link for our organization to make Aha actually useful.
i agree. it sounds great - on a first glance - to "have an integration with redmine"..but for everyday work there are so many features like the two - way integration mentioned here missing.
an integration which needs to be manually kept in sync is really not what s.o. would have in mind when a product is "integrated" ...
It has been very cumbersome to continually update statuses and timelines on both systems. Since we will not be going away from Redmine anytime soon we will probably just end up writing some kind of two-way integration ourselves until Aha can figure this out.
This integration being 2-way makes Redmine and AHA a hard pair to beat.
I agree with everyone here.
Do we have an update on if this will be worked on?
Hi, is there any update on this? I'm interested in adding Aha! into my workflow, but this integration is a must.
I have recently started with a new company and the development team use Redmine. Could you please provide an indication on when 2 way asynchronous support for Redmine on the 2.0 Integration platform is likely to happen? Migration from Redmine to Jira will delay the adoption of using Aha and to understand if there is a development plan or not.
You won't be notified about changes to this idea.