Date/time picker - Concept feedback

[#1]

Hi all!

I am looking for feedback on a concept to improve the date/time picker in Audit Log Cloud.

A consistent theme from customer feedback is to ‘enable more granular control over time’ to help pinpoint key events.

The following concept enables admins to not only choose a date range, but also the hour, minute and second in an additional time field.

The date/time picker also defaults to ‘Within 7 days’ to provide clarity on the initial date range selection.

I would love some feedback on the following:

1. Does this concept help with your use cases? If so, how?
2. Are there any further improvements or suggestions you have for the date/time picker?

Many thanks!

Jonathon and the Atlassian team

[Jonathon Conkey]

@Jimmy Seddon I was wondering if you had any thoughts on this concept given our previous discussion around audit log time parameters? Thanks!

[Jimmy Seddon]

Hey @Jonathon Conkey!

Our main use case has always been about narrowing the list of log entries to find what we are looking for.  I just checked and we have upwards of 35 within a single minute (I also noticed that the current UI doesn't actually display seconds).

I really like the concept of being able to filter the entries by a smaller date/time unit of measurement.  as far as typical usage I think it would look like this for me:

• Hours - Always
• Minutes - Sometimes
• Seconds - Rarely/Never

I hope that helps!

[Josh]

@Jonathon Conkey this is a completely different platform but I'm hoping the concept will translate well - in Power BI there is a visual that allows dates to be filtered at different hierarchy levels.

 

I could see it being helpful to show time in the audit log as a slider with different selection options:

1. Month (maybe)
   1. Week
      1. Day
         1. Hour
            1. Minute (or 15-minute increment)

I am with @Jimmy Seddon that Seconds is probably too granular. In 95% of our use cases, 15-minute increments are the most granular unit of measurement that we need to go to.

Relative timeframes can also be helpful. I'm not sure how well that would translate to the slider concept above though; filled with internal conflict over here haha.

[Jonathon Conkey]

Many thanks @Jimmy Seddon and @Josh. This is very helpful.

I have attached an updated concept below with seconds removed so the time field only contains hours and minutes.

Does this version better meet your needs?



 
The slider UI is a very interesting idea @josh 

Is it something you could see being used with the audit log table as it stands or perhaps for a view that might help visualise trends from the audit log within the chosen slider range?

Thanks,

Jonathon

[Josh]

@Jonathon Conkey I like the updated concept without the seconds. That would definitely be helpful for us.

The slider was something I was thinking about within the audit log table UI. We typically do not look the audit log from a trending perspective; it's primarily used for troubleshooting or verifying specific events. As our team's practices mature, I could see there being value in audit log trend analysis but it's not at the forefront for us currently.

[Rudy Holtkamp]

I would prefer to be able to see/search also on seconds. This way you can relate it more easily to data from other systems.

[Jonathon Conkey]

Thanks for this @Rudy Holtkamp. In terms of searching, we're exploring having hours and minutes in basic mode and seconds included as part of audit log query language. 

What are your typical use cases be when relating the data to other systems and how do you currently do that? eg Is the timestamp that is currently used in the CSV export beneficial? Where would it benefit you most to see this more granular information in the UI? 

Kind regards,

Jonathon

[Robert Nadon]

As an admin for over a decade I personally have not needed to go down to the second, what would help me more would be be able to specify multiple ranges with an OR.

[Jonathon Conkey]

Hi @Robert Nadon. The team are currently working on audit log query language which will enable you to specify multiple ranges with an OR. We will provide updates on this group when that is available.

Many thanks,

Jonathon

[Rudy Holtkamp]

@Jonathon Conkey Normally I'm searching on date and have to scroll through the entries of that day. If I have an exact time, I could pin point the event immediately.

Using hours and minutes will of course help me a lot, but why omit the seconds. I can't imagine that it would be harder for your team to implement it.

[Jonathon Conkey]

Thanks @Rudy Holtkamp. What we're working towards is covering a large number of use cases in 'Basic' mode with the date and time picker component (hh:mm) and then allowing more advanced queries in 'ALQL' (audit log query language) to help pinpoint exact events, multiple ranges and open up a wider range of filtering possibilities. This could end up looking something like below.

[Rudy Holtkamp]

@Jonathon Conkey that will be perfect!

[Jonathon Conkey]

That's great @Rudy Holtkamp! Pleased to hear it.

Thanks,

Jonathon