RELATED IDEAS
Improve Attachment Management for Ideas / Features / Epics
What is the challenge? |
There are multiple ways to add attachments to ideas/features/epics. The only standard attachment field is on the description. When creating work requests, must move attachment to description to carry over. When integrating with azure devops, must move attachments to description to carry over to azure devops. Additionally, there is not one single view of all attachments on a given record. |
What is the impact? |
Manual work and frustration. |
Describe your idea |
Ability to have a single standard attachment field and all attachments have that API key. Have a single view of all attachments in a given record. |
© 2024 Aha! Labs Inc.•All rights reserved
Comcast Advertising has a need for this as well. We need to use custom note fields to include rich formatting, which by default, includes the attachment option. We also heavily use the Aha integration with Jira, and the only field that brings attachments into Jira is the Description field. A single standard attachment field would work, or the ability to not include attachments as an option to a custom Note field would work for us as well.