Feature Request Transparency

Question

I've recently been paying closer attention to feature requests and the responses they receive. Often, I see replies along the lines of, "We’ll pass that on to the developers."

However, many of these requests seem to be quite old, and it's unclear whether any progress has been made. I understand there could be a number of reasons for this—technical limitations, resource constraints, shifting priorities, or simply a decision that the effort required may not justify the outcome.

With that in mind, I wanted to ask: is there a centralized list of requested features that includes their current status from the LM team's perspective? Specifically, it would be helpful to know:

What stage of development (if any) a request is in
The priority level assigned to it
Whether it's planned for a future release or update
A development roadmap outlining features expected (or proposed) for release over the next year, regardless of whether they originated from community suggestions

If such a list exists, where can I find it? And if not, could this be considered as a potential improvement? I believe having this kind of visibility would go a long way in helping users track progress, prioritize their own requests, and better understand which ideas are gaining traction.

matt_whitney · Answer

I agree with Bill that it would be helpful to have a centralized list of feature requests that is visible to all LM users so that we can see what the current status is. Whether they are planned for a specific release, or if they are actively being looked at by the devs, or if they are de-prioritized and in a backlog.

This would not only help give users visibility into the status of their own requests, but would also help users see if a problem they are having already has an open feature request and what the status/progress of it is.

Right now it does seem like we as users identify problems/improvements and make feature requests, but then get no update and no feeling of progress.

dave_lee · Answer

Visibility over feedback/product requests has been something weve often mentioned to our CSM over the last few years.

We used Atlassians JIRA and Confluence products. I believe Logicmonitor do too. Atlassian make they product feedback public, so you can add votes to existing feedback items raised by other users, add comments to existing feedback and subscribe to updates for specific items of feedback. It's easy to find other feedback, see comments from others, and get notified if the feedback is implemented into the product.

Something similar from logocmonitor would be great. We're often told by support and CSMs to raise feedback via the portal, but never get any feedback on it.

dave_lee · Answer

If I could throw my 2c in...Atlassian seem to do this fairly well to managing user feedback for their products.&nbsp; They allow users to create Bugs and Suggestions, vote on existing ones created by other users, add comments, subscribe to updates, etc.&nbsp; It looks like these are all logged into Jira, which I think Logic Monitor is already using.https://jira.atlassian.com/projects/Making something like this available to customers and partners would be great.&nbsp; I'm sure it would make things easier for LM as well.&nbsp; &nbsp;It must be a lot of work for LMers to correlate the different feedback users are giving, for CSMs to track what's been implemented, etc.

skydonnell · Answer

Thanks for sharing your thoughts Bill!
We now have a centralized experience where all community feedback requests are tracked for visibility and accountability. That said, due to the volume and complexity of incoming requests, we don’t have a simple way to push regular updates on each one.
We’d love your input: What have you seen work well elsewhere when submitting feature requests? Are there key points in the lifecycle where you think updates are most important? Would you be open to engaging with us more deeply as we iterate on this process?

billbianco · Answer

We now have a centralized experience where all community feedback requests are tracked for visibility and accountability. That said, due to the volume and complexity of incoming requests, we don’t have a simple way to push regular updates on each one.

Is that link published, and if so where can I find it? I understand that it is tough to provide tracking on ALL incoming requests, but insight as to what requests are being addressed and scheduled ETA would be a much smaller lift not to mention helpful for the customer base.

Forum Discussion

Feature Request Transparency

8 Replies

Recent Discussions

DataSource/Property Source that monitors Cisco End of Life (EOL) or End of Support (EOS) dates.

Collector configuration management - API/Ansible

Alert Exports : Please add export to CSV option

Active Discover Filters with non-existent properties

Service nesting and topology mapping