RELATED IDEAS
Release Roadmap Start On & Due On not working well with JIRA
We're using custom fields "Start Date" and "Planned Done Date" on our JIRA epics extensively, and we sync JIRA epics with Aha features. And we've added "Start Date" and "Planned Done Date" as custom fields in Aha features.
When we use the Releases > Roadmap page in Aha, and add an epic/feature to the timeline, it automatically adds Aha's Start On and Due On fields to the epic/feature. However, now we have some problems:
1) Start On is not sync'd with any fields in JIRA, and we can't pick it from the JIRA integration. Due On is sync'd with the Due Date field in JIRA, when we'd like to sync it with Planned Done Date instead (but not possible in the JIRA integration).
2) We now have duplicate fields. Start On = our Start Date custom field, and Due On = our Planned Done Date custom field.
Could we either allow the Releases > Roadmap to use our Start Date and Planned Done Date custom fields for the timeline values, or change the JIRA integration so that it can sync Aha's Start On => JIRA Start Date custom field, and Aha's Due On => JIRA Planned Done Date custom field?
-
ADMIN RESPONSEDec 14, 2017
We have launched an enhanced Jira integration. This integration will give you the ability to map Aha! default fields such as Start on and Due on dates to Jira custom fields, along with several other new capabilities including the ability to:
- Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
- Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from Jira)
- Automatically send outgoing changes from Aha! or choose to review and approve them
- Import records directly from Jira to make getting started in Aha! easy
Check out the blog post for more details.
There is still no start date in the epics list from Jira to map to that I can see?