Skip to content

Last updated

Project tracking · data connector

Automated Jira reports, delivered on schedule

Rahoto connects to Jira Cloud through Atlassian sign-in with read-only Jira scopes (read:jira-work and read:jira-user), and stays signed in so a scheduled refresh runs without you. It reads issues, projects and users, and you can narrow issues to one project by its key.

Connect Jira Read connection guidance

What Rahoto reads

Three Jira objects

Each object comes with the fields Rahoto reads by default, listed here exactly as it requests them.

What Rahoto reads from Jira, with the fields it requests
Object Fields
Issues

key , summary , description , status , priority , assignee , reporter , created , updated , issuetype , project

Projects

id , key , name , projectTypeKey , lead , description

Users

accountId , displayName , emailAddress , active , accountType

How you connect

What you need before connecting

Sign-in
Atlassian sign-in (OAuth)
Access requested

read:jira-work , read:jira-user , offline_access

You provide
  • A project key, to read issues from one project (optional)

Connectors read from your sources and are read-only by default. See the connection guidance for the steps.

How it refreshes

Refreshed on your schedule

Refresh mode: Snapshot.

  • On each scheduled run Rahoto takes a fresh snapshot of the data and rebuilds the report from it.
  • You can preview the data before you bind it to the page.
  • Before an issue goes out, Rahoto checks the pages and notices when a source changed shape.
  • Jira limits how fast its API can be read, and Rahoto paces its requests to stay within that limit.

Where the report goes

Delivered where your readers already work

Slack
thread or channel
Teams
channel post
Email
inline or attached
Web
viewer or embed
Webhook
your endpoint
S3
bucket drop
Drive
shared folder
SFTP
your server

Web publishing is on every plan; the other seven channels come with every paid plan. PDF, PowerPoint and PNG travel on any of them.

An example report

Weekly delivery report

Every Friday afternoon, built from Jira.

  1. A cover with the week and the projects it covers
  2. Issues by status, as a chart
  3. A table of issues updated this week, with priority and assignee
  4. Issues by project
  5. A page of risks and decisions

The structure of a report, with no figures shown. You design the pages; Rahoto binds them to the data and sends them on schedule. See finished examples in the sample gallery.

Connect Jira and set the schedule

Bind it into the document, check a run, and choose where it goes.

Start 14-day trial Read connection guidance