What Firstweek reads from Jira
- Issues, sprints, epics, and project roadmaps
- Project tickets and documentation content, where Jira and Confluence share a workspace
What shows up in the briefing
Jira content typically anchors the priorities and current-state sections - what the team is working on right now, and how it fits into the broader roadmap.
Read-only, and nothing raw is ever stored
Every integration - Jira included - connects read-only. Firstweek can never write to, modify, or delete anything in your tools. Jira content is processed in memory and never persisted; only AI-generated summaries, and opt-in source snippets up to 200 characters, are saved.
Full detail: read the trust & security page for the complete data-handling policy, or the subprocessors list for exactly what Jira data category is disclosed.
See what a real briefing built from sources like Jira actually looks like.
See a sample briefing →