When importing records from JIRA, allow Aha! to overide the directionality of fields configured in the integration

I have a JIRA 2.0 Integration with Aha! Features mapped to Epics in JIRA.

I set the directionality of the name and description fields to be one way from Aha! to JIRA. Other fields can be mapped as required.

When I perform an import from development system, it fails the import due to the directionality of the fields being Aha! to JIRA only on these compulsory fields (They need to at a minimum allow information to flow from JIRA to Aha! for the objects to successfully import).

This is problematic for a number of reasons:

  1. This can be confusing for many users that may not understand what is going on driving errors and potentially support calls.

  2. It may be necessary to have a specific mapping configuration just for importing and then changing that to the desired mapping for normal integration use

  3. The 2nd issue/situation is compounded when an integration template is configured in the manner described above with a large number child integrations all needing to be overridden or modified just for an import (which may not be one off and done in tranches over weeks/months)

There should be the ability to either:

  1. Not allow users to configure the integration in a way that it fails for some other activity or, preferably;

  2. Create a way to define new mappings for importing purposes only or to override the mappings (or at least directionality) of the integration itself temporarily during import.

Thank you for your consideration!

  • Justin Woods
  • May 21 2020
  • Future consideration
Release time frame
  • Attach files
  • Admin
    Kelly Sebes commented
    23 May 12:48am

    Thanks for the idea! We will investigate and consider adding it to our roadmap.

  • Guest commented
    21 May 04:08pm

    Absolutely agree with the above. When choosing to "import from Jira" it's clear that the user desires to bring information in from Jira. Therefore, aha! should ignore directionality on the mapping and allow the information to come in. A warning such as, "you are overwriting the directionality of field X" could be nice, but an error defeats the purpose of having the ability to import records from Jira independent of an ongoing integration.