Setting Up Automation Rules (Issue Status, Sprint, and Release Triggers)
Overview
FastDoc supports three types of automation triggers to help teams generate and publish documentation automatically:
Issue Status Change
Sprint Completion
Release Version Marked as Released
Each automation rule is configured using FastDoc’s no-code builder and follows a simple 3-step process: Trigger → Document Attributes → Publishing.
These automations help reduce the manual effort required to create product updates, release notes, or internal summaries—keeping GTM, support, and stakeholders always in the loop.
Automation Rule Types
1. Issue Status Change
Use this rule to generate documentation based on the lifecycle of individual work items (like bugs, tasks, or stories). It's perfect for teams that want to generate contextual updates—such as help articles when a feature is done, or release notes when a bug is fixed—without waiting for a larger sprint or release milestone. This ensures smaller but important updates are never missed. Trigger a document when a Jira issue (task, story, bug, etc.) changes status.
Step 1: Configure Trigger
Select Issue Status Change as your trigger.
Choose the Jira project and issue type to monitor.
Define the status or status category that should trigger document generation.
You can limit the scope to issues assigned to you, reported by you, or include all matching issues.
Step 2: Document Attributes
Choose from any of FastDoc’s supported document types:
Release Note
Help Article
Technical Document
FAQ
Marketing Copy
Sales Pitch
User Guide
Select the desired length (Short, Medium, Long).
Customize the Goal to tailor how the document should be written.
Choose whether to include attachments, child issues, or comments.
Step 3: Publishing
Connect your Confluence account.
Choose the space where documents should be published.
FastDoc will tag you in a comment on the published doc.
2. Sprint Completion
Ideal for Agile teams that run recurring sprints, this rule helps capture the outcome of every sprint cycle and turn it into a clear, structured sprint summary. It's a great way to keep leadership and cross-functional teams informed without adding manual work. FastDoc automatically includes issue movement data, helping teams reflect on what was completed, what carried over, and what needs attention. Trigger a document when a Jira sprint is marked as "Completed."
Step 1: Configure Trigger
Select Sprint Completion as your trigger.
Choose the Jira project and board where the sprint is tracked.
Step 2: Document Attributes
Document type is fixed to Sprint Summary.
Select the summary length (Short, Medium, Long).
The summary will include completed, incomplete, and carried-over issues.
Step 3: Publishing
Choose the Confluence space.
FastDoc will publish the Sprint Summary and tag you in a comment.
3. Release Version Marked as Released
Use this rule to ensure that every time a release is finalized in Jira, stakeholders receive an accurate and timely summary. It helps GTM teams prepare announcements, support teams get ahead of questions, and leadership stay informed about delivery. This trigger ensures no release goes undocumented—even when teams are shipping frequently. Trigger a document when a project version is marked "Released" in Jira.
Step 1: Configure Trigger
Select Release Version as your trigger.
Choose the Jira project.
FastDoc will detect when a new version is marked as released.
Step 2: Document Attributes
Choose from any of the seven supported document types listed above.
Select the document length.
Set a Goal to guide content generation.
Optionally include child issues, attachments, or comments.
Step 3: Publishing
Choose the Confluence space.
FastDoc will publish the document and tag you in a comment.
Reminders & Tips
You can configure multiple automation rules per project.
Documents are editable after they’re generated.
Ensure your project data is up-to-date (status fields, sprint boards, and version releases).
Automation runs in the background—no manual triggering needed.
Need Help?
Check out our help center or contact FastDoc support at contact@fastdoc.io if you need help setting up automation.