Mapping-only template Jira integration

When using an integration template to connect Aha to Jira, the child integrations inherit the Jira project from the original template. This causes authentication issues if the user doesn’t have admin rights to that specific Jira project. It also misleads users, who expect templates to serve as configurable starting points—not to lock them into prior project-level settings.

This behavior creates unnecessary friction for product managers during setup, increases support needs, and discourages the use of integration templates—reducing their intended efficiency. It can block progress for users who aren't Jira admins, and it undermines confidence in reusing templates across teams.

Decouple project-specific data from integration templates. Enable templates to preserve mapping configurations only (e.g., field mapping, issue types, statuses) while prompting users to select or configure their own Jira project during setup. This would make templates more scalable and usable across different teams, while avoiding unintended access or authentication issues.