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:
This can be confusing for many users that may not understand what is going on driving errors and potentially support calls.
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
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:
Not allow users to configure the integration in a way that it fails for some other activity or, preferably;
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!