Configure different Requirement types

What is the challenge?

There is no visibility in Aha! what issue type the Requirement is in Aha!. In addition, we'd like to create Design tasks in Aha! which don't require sync to Jira, whereas we'd like to sync Backlog Items, Activities, and Bugs from Jira to Aha! to ensure correct progress tracking on Feature, Epic and Initiative level.

What is the impact?

Currently, there is no differentiation between different requirements, hence, it's a wild mix of different things. The design team can't find their design tasks easily if we sync the Jira issues (BLI, Activity, Bug) as requirements, too.

Describe your idea

Introduce a configurable Requirement Type, similar to the Feature Type. In this way, we could a) filter Requirements and easily identify Design tasks, and b) define the integration mapping more detailed to decide what shall be synced and what not.