Allow record mapping to Asana Projects

Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every project created in Asana (which could be numerous). With multiple projects, this is very unmanageable and also limits the ability to truly track the important elements of a project like dates, artifacts, custom fields, etc.

Need to be able to map Asana projects to Initiatives, Releases, Epics or Features to leverage all of the functionality of these records. Requiring the selection of a project as part of the integration configuration prohibits this.