Copying an epic should also copy the associated features
Currently, if I want to copy a Master Feature, I must copy the Master Feature, then copy each associated Feature and map them to the Master Feature. This is time consuming and doesn't make a lot of sense.
doug evans
about 6 years ago
in Epics
9
Future consideration
Currently, the user can link a feature to a master feature by searching by feature id. However, the user is unable to link a master deature by searching by master feature id. This creates an inconsistent user experience
Keith Davenport
about 6 years ago
in Epics
3
Future consideration
We use Master Features a few different ways:
A group of related features
A use case that requires work (features) from different products.
A feature that will be implemented in different products at different times (each of those would be a fea...
Julia Doyle
about 6 years ago
in Epics
1
Future consideration
Allowing Release IDs to be imported with Master Features
When importing multiple Master Features that are all for different products and releases it is currently not possible to specify where you want each one to go. I would like to be able to with a single import be able to say that Master Feature A go...
Guest
over 6 years ago
in Epics
0
Future consideration