In 1.0 you had the option with JIRA to link to existing records.
This would let you connect an existing record in Aha! with an existing record in JIRA.
This support should exist for 2.0 integrations.
Absolutely essential considering the ability to delete the existing link, but there is no way to re-associate.
Loosing this feature is really making out lives tough now. We used it all the time.
Ron please do not forget about possibility to link Initiatives with Epics. Any Epic from any JIRA project to any Initiatives in any Product.
Thank you for the feedback. We are actively working on an update which will provide the ability to "link to existing" records for 2.0 integrations.
Agreed with Denis, I'm not stuck in a bad place, having updated from 1.0 to 2.0 but losing this feature has me thinking I need to roll back to 1.0 since we use this feature A TON. Ugh.
We should be able to link to both existing Features and Requirements.
If I had known this feature was removed from 2.0 I would have stayed on version 1.0.
Hm. This could be a barrier to adopt 2.0. I use this feature all the time as I switch back-and-forth with Jira.
Absolutely essential considering the ability to delete the existing link, but there is no way to re-associate.
Loosing this feature is really making out lives tough now. We used it all the time.
Ron please do not forget about possibility to link Initiatives with Epics. Any Epic from any JIRA project to any Initiatives in any Product.
Thank you for the feedback. We are actively working on an update which will provide the ability to "link to existing" records for 2.0 integrations.
Agreed with Denis, I'm not stuck in a bad place, having updated from 1.0 to 2.0 but losing this feature has me thinking I need to roll back to 1.0 since we use this feature A TON. Ugh.
We should be able to link to both existing Features and Requirements.
If I had known this feature was removed from 2.0 I would have stayed on version 1.0.
Hm. This could be a barrier to adopt 2.0. I use this feature all the time as I switch back-and-forth with Jira.