Skip to content

DOCS-1830 - Differentiate and consolidate time-range documentation - #7063

Open
JV0812 wants to merge 1 commit into
mainfrom
DOCS-1830
Open

DOCS-1830 - Differentiate and consolidate time-range documentation#7063
JV0812 wants to merge 1 commit into
mainfrom
DOCS-1830

Conversation

@JV0812

@JV0812 JV0812 commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

Purpose of this pull request

This pull request differentiates and consolidates four docs covering overlapping time concepts, per the ticket.

Changes:

  • time-range-expressions.md becomes the canonical page for relative/absolute time-range expression syntax. Added a new "General rules" section consolidating rules that were duplicated (and drifted) in set-time-range.md: 24-hour/12-hour time entry, mm/dd/yyyy date entry, Custom-picker quick-adjust abbreviations (with the m=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 in time-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.md trimmed 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 by time-range-expressions.md. Added a link to time-range-expressions.md for the actual syntax rules, and a note pointing to use-receipt-time.md/use-searchable-time.md for the "which timestamp field" question.
  • time-reference.md trimmed 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.md and use-searchable-time.md each get a disambiguation note clarifying they're two of three timestamp-field options (message time is the default), cross-linking to each other and to set-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

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/DOCS-1830

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).
@JV0812 JV0812 self-assigned this Aug 26, 2026
@cla-bot cla-bot Bot added the cla-signed Contributor approved, listed in .clabot file label 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

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## See also
## Additional resources


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

@kimsauce kimsauce Aug 26, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants