What is the challenge? |
When images are added to Aha! records via the API, there is currently no way to define their display size. Images default to their original dimensions and must be manually resized in the UI afterward. This creates a gap between automated content creation and the final presentation quality, especially for teams that rely heavily on integrations, scripts, or migrations. |
|---|---|
What is the impact? |
Teams using the Aha! API to generate ideas, features, requirements, or documentation cannot fully automate content creation. Manual post-processing is required to resize images, which reduces efficiency, introduces inconsistency, and increases the risk of formatting errors. This is particularly impactful for organizations syncing content from external tools (e.g., documentation systems, design tools, support platforms) where image sizing is already known and should be preserved. |
Describe your idea |
Extend the Aha! API to allow image sizing to be explicitly defined when images are inserted into rich text fields. |