-
Notifications
You must be signed in to change notification settings - Fork 886
Host specific tooltips on last opened time #32064
Copy link
Copy link
Labels
#g-softwareSoftware product groupSoftware product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.~assisting qaThis issue can be QA'd by anyone outside the QA team when capacity allowsThis issue can be QA'd by anyone outside the QA team when capacity allows~frontendFrontend-related issue.Frontend-related issue.~timeboxA task that is completed in a predetermined amount of time.A task that is completed in a predetermined amount of time.
Milestone
Metadata
Metadata
Assignees
Labels
#g-softwareSoftware product groupSoftware product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.~assisting qaThis issue can be QA'd by anyone outside the QA team when capacity allowsThis issue can be QA'd by anyone outside the QA team when capacity allows~frontendFrontend-related issue.Frontend-related issue.~timeboxA task that is completed in a predetermined amount of time.A task that is completed in a predetermined amount of time.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Done
Problem
last open time is not clearly defined and means different things on different platforms. We get different results from osquery about what last opened time is on mac vs windows/linux
Related to issue #29061
Potential solutions
Add tool tips to help explain
Figma
What is the expected workflow as a result of your proposal?
Depending on the host platform be more clear about what the last opened timestamp is actually showing.
Macos
vs
windows/linux