Create intermediate Works with: Any AI

Update an Existing Jira Story From New Information

Structured brief Has example

• 🧭 Jira

Merge new decisions into a story without losing its history.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Update an existing Jira story using new information. The current story (summary, description, acceptance criteria, estimate, comments in date order): [CURRENT_STORY]. The new information, for example a meeting note, stakeholder email or Slack discussion: [NEW_INFORMATION]. Who agreed to the change and when: [WHO_AND_WHEN]. Work already started or finished on the story: [PROGRESS].

First compare the two texts and list what is new, what contradicts the current story, what only adds detail, and what is still unclear. Then produce the updated description and acceptance criteria in the same format as the current story, marking each changed line '(changed)' or '(new)' so a reviewer sees the difference at a glance. Do not delete earlier criteria silently; list any removed criterion with the reason. If the change alters the size, say so and suggest whether to re-estimate, split the story, or create a new one for the added part. Flag any change affecting work already completed and suggest a note for the developer who started it.

Use only what I pasted, mark assumptions [VERIFY], and tell me if the new information is too vague to act on. The result should be understandable by someone who read the old version but not the discussion.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Invented current story: 'As a customer I want to download invoices.' Criteria: PDF with order number and total. New information (meeting, 12 March, agreed by product owner): invoices must also show tax and be available for the last 24 months.
Change summary: (new) criterion 3, the PDF shows tax by rate; (new) criterion 4, invoices from the last 24 months are listed; (changed) description mentions finance's request. Estimate: the 24-month list may need a new query, so re-estimate from 3 to 5 points. Comment: 'Updated after the 12 March meeting: tax display and 24-month history added at finance's request; agreed by Priya. Estimate to be reviewed.'

• structured
• jira