What is the challenge? |
We have begun tracking high-level Requirement information in Aha! and have seen that when we copy a feature the stories are also copied. This may be appropriate in some cases, but not all. |
What is the impact? |
This may create unnecessary duplicate stories that have to be deleted before integration with our ALM |
Describe your idea |
When copying a feature that has Requirements related to it, give the user and option to copy the stories or to not copy stories. |
As you consider this idea, would you also extend this potential functionality to To Dos, as well? We are finding a similar situation with To Dos. Both duplicating Requirements and To-Dos is becoming a pain point for our users. Thank you.
We too have scenarious where we need to duplicate the feature but don't want the requirements (stories) to come over.