All pieces of Feedback are either in your Savio Inbox for traiging/sorting, or already linked to a Feature Request. The Feature Request already has Product and Product Area fields assigned to it. Why would any individual piece of Feedback need to have a different Product or Product Area than its parent Feautre Request? So far from me, I don't see any benefit at all. In fact, it is a daily struggle of extra work and various errors.
No benefit to assigning Products and Product Areas in your individual Feedbackpieces that are different to thir parent Feature Requests.
Adds more work and more room for error. For some reason (user error, sorting mistake, etc.), some pieces of Feedback have Products and Product Areas that are different to their parent Feature requests - needs to be reviewed and corrected (more work).
UI is messy and cl;uttery, with unneeded elements. If I view a Feature Request, every single piece of feedback under it hahe the Products and Product Areas showing. completely unnecessary, waste of space, and distracting.
Sometimes you have to rethink and reorganize your Products and/or Product Areas. Once done, you have to migrate the Products and/or Product Area in all the child Feedback pieces belonging to that feature request too.
More UI clutter and useless time-consuming steps during submission. Every time you add Feedback to an existing Feature Request, you have to assign Products and Product Areas. Shoulf show up only when submitting a new Feature Request.
Does anyone see a reason for having this at all? Individual pieces of Feedback should only have unique Tags assigned to them; Products and Product Areas should apply to Feature Requests exclusively.
Activity
All pieces of Feedback are either in your Savio Inbox for traiging/sorting, or already linked to a Feature Request. The Feature Request already has Product and Product Area fields assigned to it. Why would any individual piece of Feedback need to have a different Product or Product Area than its parent Feautre Request? So far from me, I don't see any benefit at all. In fact, it is a daily struggle of extra work and various errors.
No benefit to assigning Products and Product Areas in your individual Feedbackpieces that are different to thir parent Feature Requests.
Adds more work and more room for error. For some reason (user error, sorting mistake, etc.), some pieces of Feedback have Products and Product Areas that are different to their parent Feature requests - needs to be reviewed and corrected (more work).
UI is messy and cl;uttery, with unneeded elements. If I view a Feature Request, every single piece of feedback under it hahe the Products and Product Areas showing. completely unnecessary, waste of space, and distracting.
Sometimes you have to rethink and reorganize your Products and/or Product Areas. Once done, you have to migrate the Products and/or Product Area in all the child Feedback pieces belonging to that feature request too.
More UI clutter and useless time-consuming steps during submission. Every time you add Feedback to an existing Feature Request, you have to assign Products and Product Areas. Shoulf show up only when submitting a new Feature Request.
Does anyone see a reason for having this at all? Individual pieces of Feedback should only have unique Tags assigned to them; Products and Product Areas should apply to Feature Requests exclusively.