Range() start and stop relative values should not crop graphs based on the data that's returned

[asalem1]

Problem

Using the dateTimePicker to set the timeRange of a query beyond the confines of the data will display blank parts of the graph when data does not exist. However, when using the range() function in the script editor in conjunction with relative times, the view only displays the data that's returned and not the entire range:

|> range(start: time(v: "2020-03-03T12:00:00Z"), stop: time(v: "2020-03-04T12:00:00Z"))

OR

|> range(start: -12h, stop: 4h)

These should apply the same effect that using the daterangepicker does on the graph view. Related to #15908

[ziebelje]

I found you can work around this by adding an aggregateWindow where the every matches your data interval. I don't know that it would work in every situation but it's helpful for me.

[rickspencer3]

My view is that the current design is good, fwiw

[ziebelje]

The reason I would prefer it to use the entire time range is so I can build a dashboard and properly compare graphs on it. If I have three graphs, and the third one is still a new metric, I won't be able to line up anything when I'm moving my cursor over the charts.

These look nice because they all have a full range of data. If I added a new metric it would take a week (or longer for longer ranges) to be possible to quickly correlate two charts.

[asalem1]

This is still an issue