Docs: clarify draft filter behavior in Manage Posts (408513)

[cursor]

Jira

• https://vendasta.jira.com/browse/SM-3785

Change classification

• Feature behavior change (UI behavior in draft listing context)

Summary of documentation updates

• Updated existing page:
  • docusaurus/docs/multi-location-business-app/social/manage-posts-social-multi-location.mdx
• Added a concise subsection, Filtering drafts by context, under the existing How to use managed posts section.
• Documented current behavior:
  • Calendar / Report context lists drafts by scheduled date
  • Post Menu context lists drafts by updated date

Existing docs updated vs new docs

• Updated existing docs only
• No new page created

Placement reasoning

• The Jira change is about draft-list behavior in social post management.
• The existing Manage Posts page already documents draft/scheduled workflows and is the closest canonical location.
• Adding a focused subsection there keeps behavior guidance in one place and avoids fragmenting social posting documentation.

Acceptance criteria coverage

1. Introduce a filter option to sort or filter drafts.
   • Covered by the new Filtering drafts by context section.
2. If the filter is set to calendar/report, drafts should be listed by scheduled date.
   • Explicitly documented as Calendar / Report → scheduled date.
3. If the filter is set to post menu, drafts should be filtered by updated date.
   • Explicitly documented as Post Menu → updated date.

Visual inputs (Figma/images)

• Jira payload included an attachment reference, but the image content was not accessible from this automation environment.
• Documentation update was based on Jira acceptance criteria and issue context text.

Skills used

• /workspace/.cursor/skills/sprint-review/SKILL.md (release-safe, existing-doc-first update pattern)
• Repository discovery tools: rg, Glob, ReadFile

Assumptions / limitations

• Linked implementation PR author details for SM-3785 were not resolvable from available GitHub search results in this environment, so no additional implementation-author tags were added to avoid incorrect tagging.

Mentions

@ahnikakuse
@haleyserrano
@maryam6samadi