Configuration
Configuration
Fine-tune StoryLoop's behavior to match your team's workflow, terminology, and code context.
AI Settings
The AI Settings tab controls how StoryLoop writes content — its voice, structure, and output format.
Custom Templates
Configure templates for different issue types so the AI always follows your team's structure. For best results:
- ✓ Set separate templates for Bugs, Stories, and Tasks
Set up Example Issues
To stick to your team's style, provide a few "gold standard" example issues for each issue type. The AI will use these examples as a reference when generating new content.
- ✓ Provide a few "gold standard" example tickets in the template
- ✓ Set separate examples for Bugs, Stories, and Tasks
Project Context
The Project Context tab is the single most impactful setting for output quality. Feed the AI background knowledge about your product so it stops generating generic tickets.
💡 Rule of thumb: the more detailed your Project Context, the less you need to explain in individual tickets. If the AI knows what your "Admin Gateway API" is, you only have to mention its name.
Useful things to include:
- →Application architecture overview (which services exist, how they communicate)
- →Domain-specific terminology and acronyms used by your team
- →User personas and their goals
- →Key technical constraints or non-functional requirements
- →Links or names of related internal systems
GitHub Integration
Connect your GitHub workspace to allow StoryLoop to reference pull requests, branches, and code commits when generating issue descriptions.
- 1
Open the GitHub Integration tab in Project Settings → StoryLoop.
- 2
Click "Connect GitHub" and authenticate with your GitHub account.
- 3
Select the repositories relevant to the current Jira project.
- 4
Save. StoryLoop will now use code context when generating issues for this project.