# stories.example.txt
# Input file for create-jira-stories.sh
#
# Lines starting with '#' are comments.
# Stories are separated by a line that is just: ---
#
# Single-line fields below are "sticky" -- set them once and they apply to every
# following story until you change them. Override any of them inside a story.
# Size is intentionally never set.
#
# EPIC is also sticky: it attaches each following story to an ALREADY-EXISTING
# epic (passed to jira-cli as --parent). Set it once near the top to link the
# whole batch; change it to switch epics, or set it blank to stop attaching.
#
# Optional per-story fields (omit to leave unset):
#   FIX_VERSION:       <release name, e.g. "privacy-policy-administration-service: Release A">
#   STORY_POINTS:      <number, e.g. 3>
#   ORIGINAL_ESTIMATE: <time, e.g. 2d, 4h, 30m>
#   ID:                <local alias for THIS story, e.g. "date-roundtrip">
#   AFTER:             <alias(es)/key(s) this story must be done AFTER; the
#                       script links each as "<this story> is blocked by <that>".
#                       Comma/space separated; may mix local IDs and real keys.>

PROJECT:   CKM
COMPONENT: privacy-policy-administration-service
TYPE:      Technical Debt
PRIORITY:  Standard
EPIC:      CKM-40000

---

# This story gives itself a local ID so later stories can depend on it. Because
# EPIC is set above, this story is attached to epic CKM-40000.
ID: date-roundtrip
TITLE: Remove redundant/incorrect date round-trip in `UserAgreementMapper`

FIX_VERSION:       privacy-policy-administration-service: Release A
STORY_POINTS:      2
ORIGINAL_ESTIMATE: 4h

VALUE:
As a maintainer of the privacy-policy-administration-service, I want the service to be
as efficient as possible so that I am able to use it better.

NOTES:
`getUserAgreementMapper(...)` does `OffsetDateTime.parse(userAgreementEntity.getCreatedDate().toString())`
— `createdDate` is **already** an `OffsetDateTime`. The parse/format round-trip is wasteful and can
throw on locale/format edge cases. Use the value directly.

ACCEPTANCE:
- mapper uses `getCreatedDate()` directly; tests unchanged/green.

---

# This story has to be done AFTER the one above. "date-roundtrip" is a local
# alias defined above -- no real ticket number needed yet. After both are
# created, the script links them so this story shows as blocked by that one.
# It is also attached to the same epic (EPIC is still CKM-40000).
ID: followup-tests
TITLE: Add regression tests for `UserAgreementMapper` date handling
AFTER: date-roundtrip

VALUE:
As a maintainer, I want regression coverage for the date mapping so that the round-trip bug
cannot silently return.

ACCEPTANCE:
- Tests cover the direct `getCreatedDate()` path and a locale edge case.

---

# AFTER can list multiple prerequisites and can mix a local ID with a real,
# already-existing issue key (e.g. CKM-39999). This story must come after both.
TITLE: Document the mapper changes in the SRVDD
AFTER: followup-tests, CKM-39999

VALUE:
As a maintainer, I want the SRVDD updated so that the service documentation stays accurate.

ACCEPTANCE:
- SRVDD reflects the new date handling.

---