I agree with everyone else here. I also think that, even if a two-way integration wasn't possible, a more detailed mapping of Aha! Feature data to Redmine data would help. For example, being able to push estimations through to Redmine from Aha!
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.
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.
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" ...
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.
Update target version in redmine when pushing updates from aha
Merged
When I send a feature from Aha! to Redmine it adds the release date (target version), description, attachments and subject but when I push through updates it only updates changes to the description, attachments and subject not the release date.
Wh...
Guest
over 5 years ago
in Integrations
0
Future consideration
16
MERGED
Enhance the redmine integration
Merged
Redmine integration is poor compare to Jira.
Can you at least add a backlink/reference to the Aha Feature in the redmine ticket ?
Guest
almost 9 years ago
in Integrations
0
Future consideration
1
MERGED
how about two way integration between Aha and Redmine. is this on your Roadmap any soon?
Merged
No description provided
Rayan Jreije
about 4 years ago
in
0
Future consideration
I maintain part of Aha! and no idea about other systems. I like Aha! Integration is a good way!
I agree with everyone else here. I also think that, even if a two-way integration wasn't possible, a more detailed mapping of Aha! Feature data to Redmine data would help. For example, being able to push estimations through to Redmine from Aha!
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.
Hi, is there any update on this? I'm interested in adding Aha! into my workflow, but this integration is a must.
Do we have an update on if this will be worked on?
This integration being 2-way makes Redmine and AHA a hard pair to beat.
I agree with everyone here.
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.
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" ...
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.