If I promote an idea to a feature then convert the feature to a requirement on another feature, there's no reference to any of that on the source idea (it's just marked as 'planned').
This is how I'd actually like the 'link to feature' feature to work (make it a requirement and link back) - currently doing so makes it look like the feature was 'promoted' from the linked idea, but often the feature existed first, I just want to make it clear that when the existing feature is implemented, the idea will be done.
Thank you for the request. As you know, requirements don't support all of the capabilities of features, so converting features to a requirement may lose some information in the linkages.
The workaround in this scenario would be to link the feature to the previous idea and you can make a mention and link in the feature description to this specific requirement that it matches.
At this time, based on current priorities, existing functionality and historical feedback, we are unlikely to make updates in this area. We hope you can understand.
this relates directly to APP-I-3348 where you marked "likely to implement". Why is this one unlikely?