When an Epic is marked Done in Jira, the system builds a clear retrospective report and sends it to Google Docs. It helps product and engineering teams share outcomes fast and keep a clean record of what happened. Managers save time, and the team gets consistent write ups after each Epic closes.

Here is how it works. A Jira event listens for issue updates, then a check confirms the Epic status is Done. The flow pulls all issues linked to the Epic and fetches every comment. It then groups the text, combines descriptions and comments, and feeds that into an AI agent using an OpenAI chat model with simple memory. The agent follows a set format to write an Agile retrospective. Finally, the report is inserted into a chosen Google Doc so your notes live in one place.

Setup needs access to Jira Software Cloud, an OpenAI API key, and a Google account for Docs. Add your document URL, confirm the Epic status check, and map the issue fields used for the report. Expect report prep to drop from hours to minutes, with consistent summaries ready for sprint reviews, leadership updates, and audit trails.

• On app event trigger watches Jira issue updates and runs only when the Epic status is Done.
• Retrieves all issues linked to the completed Epic using Jira get all operations.
• Pulls every issue comment and ties them to the correct issue key.
• Combines titles, descriptions, statuses, and comments into clean fields for processing.
• Summarize node concatenates all comments into one block for clear analysis.
• AI Agent with OpenAI chat model creates a structured Agile retrospective using a defined system message.
• Simple memory keeps short context so the AI output stays consistent across items.
• Google Docs node inserts the final report into a selected document for easy sharing.

• Reduce report prep from 2 hours to 5 minutes
• Automate 90% of comment review and summarization
• Improve consistency of retros with a standard format
• Connect Jira and Google Docs seamlessly
• Capture team feedback right when the Epic closes
• Support multiple Epics per week without extra effort

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Jira Software Cloud, OpenAI and Google Docs. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, connect Jira Software Cloud: double click the Jira Trigger or Jira nodes, choose 'Create new credential', and follow the on screen steps. Make sure your Jira user has permission to manage webhooks and read issues and comments.
4. Connect OpenAI: double click the OpenAI Chat Model node, choose 'Create new credential', and paste your API key from the OpenAI API keys page. Save the credential.
5. Authorize Google Docs: double click the Google Docs node, choose 'Create new credential', sign in with your Google account, and grant document access. Save the credential.
6. Open the Jira Trigger node and confirm the event is set to jira:issue_updated. Save the trigger settings.
7. Open the If node and set the condition to check the Epic status equals Done. Use the same field your Jira uses for Epic status.
8. In the Jira Get All Issues node, configure the query so it returns issues linked to the Epic from the trigger. Use your Jira field for Epic link or parent as needed.
9. In the Jira Get All Comments node, confirm the issueKey expression is set to {{ $json.key }} so comments match the correct issue.
10. Review the Edit Fields node and keep the mappings for Epic name, title, description, and status. Adjust expressions if your Jira fields differ.
11. Check the Summarize node and confirm it groups by Epic details and concatenates the Comment field into one text block.
12. Open the AI Agent node and verify the system message defines the retrospective layout. Make sure the variables map to comments, description, title, status, and epic name.
13. In the Google Docs node, paste your target document URL and keep the Insert action so new reports are added to the doc.
14. Test the flow: move a sample Epic to Done in Jira and watch the execution in n8n. Open the Google Doc and confirm the new report appears.
15. Troubleshoot if needed: if no run starts, check Jira webhook permissions. If no issues return, adjust the JQL or Epic link field. If the doc does not update, confirm Google Docs access and the document URL. If the report is empty, confirm comments are visible to your Jira user.