Conversation
Consolidate duplicate time-range expression-syntax rules (relative/absolute entry formats, timezone source, Free-account 7-day limit) into time-range-expressions.md as the canonical page. Trim set-time-range.md down to its own UI-picker mechanics with a link out. Trim time-reference.md's ingest-time timestamp-parsing scope by removing its Search-UI-specific "Time ranges" and "Date format" sections. Add disambiguation notes across use-receipt-time.md, use-searchable-time.md, and set-time-range.md so readers land on the right page among the three timestamp-field options (message, receipt, searchable time).
kimsauce
reviewed
Aug 26, 2026
| | 04/01/2017 | From midnight April 1st, 2017 to now. | | ||
| | 04/01/2017 04/02/2017 | From midnight April 1st, 2017 to midnight April 2nd, 2017. | | ||
|
|
||
| ## See also |
Collaborator
There was a problem hiding this comment.
Suggested change
| ## See also | |
| ## Additional resources |
kimsauce
approved these changes
Aug 26, 2026
kimsauce
reviewed
Aug 26, 2026
|
|
||
| Search Time Ranges can also search all data with any and all timestamps. For details, see [Use Receipt Time](/docs/search/get-started-with-search/build-search/use-receipt-time). | ||
|
|
||
| ## Date format |
Collaborator
There was a problem hiding this comment.
@JV0812 Shouldn't this Date format section stay in there? It's in the title, and I don't see other guidance like that elsewhere in the doc.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This pull request differentiates and consolidates four docs covering overlapping time concepts, per the ticket.
Changes:
time-range-expressions.mdbecomes the canonical page for relative/absolute time-range expression syntax. Added a new "General rules" section consolidating rules that were duplicated (and drifted) inset-time-range.md: 24-hour/12-hour time entry, mm/dd/yyyy date entry, Custom-picker quick-adjust abbreviations (with them=minute vs.m=months distinction called out explicitly), and the Free-account 7-day time-range limit. Also folded in the Scheduled Search timezone caveat and browser-locale date-format caveat previously intime-reference.md, and fixed a pre-existing gap where the absolute-expression section never stated that a single expression's end time defaults to "now" (only the relative section said so, despite the original rule stating it applies to all time expressions). Added a "See also" section cross-linking to the other three docs.set-time-range.mdtrimmed to its own UI-picker mechanics only (Relative/Custom/Recent options, timezone-offset display details). Removed the duplicated "Rules" section and the Free-account sentence, now owned solely bytime-range-expressions.md. Added a link totime-range-expressions.mdfor the actual syntax rules, and a note pointing touse-receipt-time.md/use-searchable-time.mdfor the "which timestamp field" question.time-reference.mdtrimmed to pure ingest-time timestamp parsing by removing its "Time ranges" and "Date format" sections, which strayed into Search-UI territory already covered elsewhere. Replaced with a short pointer note so its ~35 inbound links still land on a coherent page.use-receipt-time.mdanduse-searchable-time.mdeach get a disambiguation note clarifying they're two of three timestamp-field options (message time is the default), cross-linking to each other and toset-time-range.md.No sidebar, redirect, or ID/slug changes. Verified via full
yarn build(no broken links/anchors) and a line-by-line audit confirming every original rule from the removed sections is still captured somewhere.Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1830