Overview
Many teams use Glossa for discovery and requirements management, then send requirements to Jira for development tracking. This guide shares common practices for making that handoff smooth and effective.
Common Practice: Sprint-Based Sending
What many teams do: Send requirements to Jira before each sprint that will be worked
Why this works:
Jira backlog stays focused on current/upcoming work
Not overwhelmed with all requirements at once
Can refine requirements right before development
Easy to prioritize what's ready vs what's not
Recommended Workflow
Phase 1: Discovery in Glossa
Upload meeting recordings, docs, emails
Review generated requirements
Resolve contradictions
Generate acceptance criteria
Refine until ready
Phase 2: Prepare for Handoff
Mark requirements as "Approved" status
Organize into categories
Prioritize for upcoming sprints
Generate implementation tasks
Phase 3: Send to Jira
Select requirements for next sprint
Click "Send to Jira"
Requirements become Jira stories/tasks
Status changes to "Sent to Jira"
Phase 4: Development
Dev team works in Jira
Keep Glossa as source of truth for requirements
Send additional requirements for future sprints
Repeat process
Configuration Best Practices
Map Fields Thoughtfully
Glossa Priority → Jira Priority
Glossa Category → Jira Component or Label
Glossa Type → Jira Issue Type
Include Glossa Requirement ID in Jira field for traceability
Choose Appropriate Issue Types
Requirements → Stories
Tasks → Tasks or Subtasks
Or customize based on your team's Jira workflow
Decide on AC Handling
Include ACs in requirement description, OR
Send ACs as separate subtasks
Choose based on your team's preference
Configure Automatic Updates
During active discovery: Enable automatic overnight updates
Keeps Jira current with Glossa changes
Reduces manual re-syncing
During active development: Disable automatic updates
Prevents overwriting developer changes in Jira
Jira becomes source of truth during build
Timing Recommendations
When to Send
Send requirements when they're:
✅ Reviewed and refined
✅ Contradictions resolved
✅ Acceptance criteria generated
✅ Priority and category assigned
✅ Ready for development planning
Don't send requirements that are:
❌ Still being discovered
❌ Haven't been reviewed
❌ Have unresolved conflicts
❌ Missing key details
Batch Size
Recommended:
Send 2-15 requirements per sprint
Match to team velocity
Don't send entire backlog at once
Best Practices
Keep Glossa as Source of Truth
Glossa maintains full discovery history
Glossa has source citations
Jira for execution tracking
Don't try to manage requirements in both
Use Status to Track
Requirements not yet sent: Draft, In Progress
Requirements sent to Jira: Sent to Jira
Easy to see what's in Jira vs still in Glossa
Send in Priority Order
Send highest priority first
Keeps Jira backlog prioritized
Avoid overwhelming dev team
Communicate Handoff
Let dev team know when requirements sent
Point them to Jira for work tracking
Available for questions about requirements