Feature ideas

Correctly, If needed to display a chart in time frame X you will need to create a widget for each timeframe - not so user friendly Please add an option to choose the timeframe from a drop down this way users will be able to filter the data according to their choice and will remove duplication of widgets that shows the same data only in different timeframe

Add the ability to customize the data shown in the dashboard by a variable that can be selected by the user. Add the option to customize the variable in the URL.

Changes made to integration configs today (for example - the mapping or setting of an integration) are not displayed in an audit log tab of their own. Adding this information would make troubleshooting easier, it would also make it easier to return or review previous configurations of an integration that worked and use that as a reference to make additional updates

As a non admin user, it feels odd to see a message like "Check your data sources or add {entity name}s manually." when there are no records to display. While a different message might make more sense globally (or even distinguishing between user roles, since the current message seems more targeted at actions that an admin could take), there could also be value in allowing for a Table widget instance-specific message to be displayed when no matching entities are available to display (e.g., "You have no pull requests waiting on you!" for a list of pull requests assigned to you, or even a message that both highlights no matching entities and adds instructions for what the user should do when that situation is unexpected/undesirable: "No matching repos for your team, please ____")

Include a new blueprint of Opsgenie Comment and return the list of comments related to each Opsgenie Alert in the Opsgenie Integration.

The existing Azure DevOps integration does not support ingesting data about iterations (though the iteration path itself does come in as an attribute of a work item). Having the iterations themselves coming through as a "kind" (using the data from this endpoint ) would allow us to further refine our "my work" entity table to allow users to focus specifically on work items in the current iteration (or view different iterations in the past/future) more easily, as we could compare the start/end date of a given iteration to the current date (much like ADO allows users to do today in their sprint view).

The feature will provide a quick visual tool to determine the delta between two openAPI spec versions.

We have a use case where context is everything - and having the page that the user was on when they triggered the self-service action is an important part of that context. Potentially, this could be a part of the trigger object (potentially as a new from key, alongside the existing "origin": "UI" ?). We have tried thinking about potential workarounds, and all we have come up with so far is to either ask the user to pick which page they came from (forcing us to maintain an enum of existing pages - both unwieldy, and requires additional maintenance) or create one action per page (where the only difference between the actions is that hidden page attribute - again, quite unwieldy and adds a lot of additional maintenance).