Share your product feedback

Add a new idea Subscribe
Status Future consideration
Categories Application
Created by Guest
Created on Dec 7, 2023

RELATED IDEAS

Ability to choose how a copy functions

Who would benefit?

Anyone who needs to copy a record

What impact would it make?

Save time

How should it work?

There are several ideas for improving how the copy function works in Aha!

We have 2 specific request:

  • to be able to choose whether to copy attachments, record links and requirements when copying a feature.

  • to be able to choose whether features in other releases/workspaces are copied when copying an epic or copying a release which contains epics and therefore copies them. (The same could be true for copying an initiative which has epics and features feeding into it.

Also, here's a collection of other requests for greater flexibility when copying records.

https://big.ideas.aha.io/ideas/A-I-8171

https://big.ideas.aha.io/ideas/A-I-11389

https://big.ideas.aha.io/ideas/A-I-7981

https://big.ideas.aha.io/ideas/AFPR-I-7472

https://big.ideas.aha.io/ideas/A-I-13114

https://big.ideas.aha.io/ideas/A-I-15283

It seems to me that what Aha! user are asking for is a dialogue box to pop up between the menu containing the copy option and performing the copy which provides the user with a set of options on what the copy should do:

  • Copy children all children or children in this workspace only (with permissions warning if trying to copy records into workspaces without write access.)

  • Copy links to parents (e.g. link to epic, initiative, goal)

  • Copy record links (dependencies etc)

  • Copy attachments

  • Etc.

This would save users a huge amount of time with repeatable, mundane process that are otherwise prone to human error.

  • Attach files
  • Guest
    Jun 9, 2026

    I would like to add two additional requests:

    1. Choose to copy comments.

      • Use Case: A document was created in the wrong workspace and moved to the correct workspace. In order to ensure the document had the correct identification number with the correct workspace abbreviation in the URL, I had to copy the document. The comments from the original document could not be copied over. I had to use a screenshot on the new document to retain the information but this does not accurately display the number of comments or the tagged users.

    2. Choose to copy locked fields.

      • Use Case: We use locked fields to retain data as a snap shot in time when necessary, for example to retain which records were included in the quarterly plan of record at the time the plan was approved. When a record is copied the locked fields are automatically copied too which leads to discrepancies in data. In this example, the copied record would show that it was included in the plan of record at the time the plan was approved, despite the new record being created later and thus not included in the plan of record at the time of approval.

    Reply
  • +2
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2026 Aha! Labs Inc.•All rights reserved