Agreed...and while we're on topic of User Echo, the top 10 upvoted feature requests seem to not be going anywhere, at least according to their status'...with an average age of just under 1 year old, everything is "Pending Review", "Under Review", or have been changed back and forth as stated above.

The statuses within UserEcho are linked directly to each issue's status within Jira, our issue tracking/SDLC-managing software. What you're seeing is the issue going through each department (ie Product Management prioritizing, UI/UX being assigned and designing how it should look, and then development receiving the issue, scheduling it, and queuing it out to a developer). Basically each department/team has a 'Review' and 'In-Progress'-like status that translates somewhat poorly back into UserEcho. It's not that we're indecisive about the issue, its that the integration between Jira and UserEcho doesn't support (or we haven't configured it correctly) the different statuses in which each issue can be. I'll make sure to ask the PM who is in charge of the two investigate if there's a better way to specify the correct status within UserEcho.


Pretty much each of these items within the top 10 rated issues require significant architectural changes in order to implement. To us, this means they sit in a special 'Architect' status because they require other changes that aren't displayed/reflected within UserEcho. I guess to phrase it a little easier, if you were going to build a house, your to-do list wouldn't have a single item 'Build House'. Instead you'd break it into modular components like 'Lay Foundation' and 'Construct Walls' (probably even deeper). To us, these items in the top 10 are epics that have multiple sub-items/sub-tasks to which they are not connected outside of our issue tracking software.


We chose to use the UserEcho tool specifically because we wanted a more efficient way to listen to our customers. While this forum is a great way in which we can interact, it is extremely poor for tracking interest in features. For some of the reasons I mentioned above we know it's not perfect, but it does provide a more streamlined system to gauge priorities from people who use the application every day.

Thank you for the response Scott. I figured that might be the case. While it is helpful to better understand the situation, if it's possible to get better integration between Jira & UserEcho I think all of us here in the forum would greatly appreciate it! Thanks again.

I think just annotating which dept/division performed or is waiting on their 'review' would be a good start. That doesn't just communicate with us, but helps to keep each dept visibly accountable to your customer base.