Files
fidelity-ai-workspace/vault/03-context/process/jira-story-rules.md
david.delagneau b82194bc55 Add daily logs and templates for Fidelity project
- Created daily log entries for April 13-16, 2026, capturing standup contexts, Mattermost syncs, and ongoing work items.
- Established a daily logs index for easy navigation of daily entries.
- Introduced templates for daily notes, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Developed maps for AI workspace core, current work, Fidelity domain, and work items to enhance workspace navigation.
- Implemented base configurations for daily notes, decisions, people, systems, work items, and workstreams to streamline data management.
- Added a placeholder for attachments to facilitate file organization.
2026-04-16 16:01:19 -06:00

1.3 KiB

type, project, status, updated, tags
type project status updated tags
process fidelity active 2026-04-16
process
fidelity

Jira Story Rules

Goal

Keep Jira updates precise enough that the story reflects the real problem and remains easy to reference later.


Stable Rules

  • Preserve Jira ID and explicit title whenever available.
  • Prefer story wording that describes the real contract or behavior gap, not only the first symptom.
  • Include authenticated-state or environment qualifiers when they materially affect scope.
  • Validate consumer behavior before finalizing scope when the issue depends on Fid4 or flagship.

Story-Creation Guidance

  • Create or refine the story after the reproduction path is understood well enough to avoid mis-scoping.
  • Include points and scope only after the work has been framed clearly.
  • If the issue crosses SDK, adapter, FT modules, and consumer app boundaries, the story should say so.
  • If a bug is external or not yet confirmed as regression, avoid writing the ticket as if the root cause is already proven.

Historical Signals From Slack

  • Historical Slack threads repeatedly show Jeff refining titles and descriptions before stories were created or shared.
  • Several story discussions centered on making the wording reflect deeper SwiftUI, lifecycle, or integration issues rather than surface symptoms alone.