Hours on a project
Priya Sharma, delivery lead at Acme Ltd, asked how many hours went on project 10000 last week. Memtro listed the worklogs with totals by issue and by author. It noted that Tempo names people by Atlassian account id only.
Tempo + Memtro
How many hours did the team log on this Jira project last week?
Tempo connects Memtro to Tempo Timesheets and Planner for Jira Cloud. It reads worklogs by date, project or issue, with hours, billable hours and totals by issue and by author, plus Tempo accounts, teams and Planner resource plans. Tempo names issues by numeric Jira id and people by Atlassian account id only. When asked, and once an administrator has granted them by name, it can log or change time, permanently delete a worklog, submit, approve, reject or reopen timesheets, and plan people onto issues. Worklogs feed billing and payroll, and approval locks those hours.
In Memtro
What you can do with Tempo in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Tempo tool, reads what it needs, and answers with the source cited.
What it does
- 01Lists worklogs between two dates, with hours, billable hours, issue id, author and description, plus totals by issue and by author.
- 02Filters worklogs by Jira project id, issue id, or changes since a date.
- 03Lists Tempo accounts with key, name, status, category and customer, and Tempo teams with their lead's Atlassian account id.
- 04Reads Planner resource plans over a date window, with planned hours per day and in total for each plan.
- 05When asked and granted, logs time against a Jira issue, changes a worklog's date, hours or description, or permanently deletes it, which removes the time from billing and payroll.
- 06When asked and granted, submits or recalls a timesheet, approves, rejects or reopens it (Tempo may notify the person or reviewer), and creates, changes or permanently deletes Planner plans.
Acts when asked
When you ask it to
These tools change something in Tempo. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
- 01Log time against a Jira issue
- 02Change a worklog's date, time, hours or description
- 03Delete a worklog
- 04Submit or recall a timesheet for approval
- 05Approve, reject or reopen a timesheet
- 06Plan a person or generic resource onto an issue or project
- 07Change or delete a plan
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Tempo for you. Each event can start a job, with the event as its input. Tempo signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooks- 01Time logged
- 02Logged time changed
- 03Logged time deleted
- 04Plan created
- 05Plan changed
- 06Plan deleted
- 07Team created
- 08Team changed
- 09Team deleted
- 10Someone added to a team
- 11Team membership changed
- 12Someone removed from a team
- 13Workload scheme created
- 14Workload scheme changed
- 15Workload scheme deleted
- 16People moved between workload schemes
- 17Working days changed
In practice
Ask it like you would a colleague
Once Tempo is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Tempo + MemtroHow many hours were logged on project 10000 last week?
Who logged billable hours on issue 10234 this month?
Which Tempo accounts are active, and which customer is each for?
What is planned on project 10000 over the next two weeks?
Log two hours on issue 10234 for me today for the client call.
Closing the week
Dan Fletcher, engineering manager at Northwind, asked Memtro to log the hour he forgot on issue 10234 on Thursday and then approve Sam Lee's submitted timesheet. Memtro logged the worklog on his timesheet and approved Sam's, which locked those hours for billing and payroll.
Teams
Where it fits
The teams that lean on Tempo most, a question each of them asks, and what they connect beside it.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- OperationsMonitors and digests that run themselvesOperations lead, Analyst, Team manager, Administrator“List my jobs”Used alongside Help Scout, Stripe, Xero, Postgres, ShipEngine and 8 more.
Better together
Works with
A record in Tempo is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
- Engineering and operationsTempo with GitHubIssues, pull requests, code and commits, searchable by anyone who can ask a question.
- Engineering and operationsTempo with AWS CloudWatchLogs, metrics and alarms from AWS, answered in plain English with the query that found them.
- Engineering and operationsTempo with SentryAsk what is breaking in production and get the stack trace, not a dashboard.
- Documents and wikisTempo with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisTempo with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisTempo with ConfluenceSearch and read wiki pages, and write them when you ask.
- Email, calendar and chatTempo with GmailSearch and read mail so the last thread with a customer is one question away, and send the reply when you ask.
- Email, calendar and chatTempo with SlackSearch messages, read channel history and threads, post when you ask, and answer when mentioned.
- Email, calendar and chatTempo with Google CalendarMeetings in a window, event details, and the next two weeks synced into memory, and events it can create, change or cancel when you ask.
Also in Work management
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Clio Manage- Linear
- Jira
- Asana
- monday.com
- Airtable
- Basecamp
- Trello
- ClickUp
- Harvest
- Productboard
- Shortcut
- Todoist
YouTrack- Baserow
Canny- Clockify
- Everhour
Float
Productive
Smartsheet- Teamwork.com
- Toggl Track
Wrike
Financial Cents
Karbon
Scoro
Kanboard
Kimai
Leantime- OpenProject
- Plane
- Redmine
- Vikunja
Acuity Scheduling
Luma
Tito
Fellow
Samsara
ServiceM8
Cliniko
Fleetio
SavvyCal
Chili Piper
Humanitix
Circleback
Aha!- RotaCloud
Smoobu
Semble- airfocus
Airmeet
Beds24
Bookeo
Commusoft- Favro
Fergus
Fixflo- Hostaway
- Hostfully
Housecall Pro- Motion
Nookal
Paymo
ProductPlan
SimplyBook.me- Synchroteam
TimeCamp
Workiz- Zuper
Guesty
Buildium
Skilljar
Runn
Clockodo
Setup
How to connect
Connect withTempo API token and optional region
- 1
In Jira, open Apps → Tempo → Settings → Data Access → API integration. Create a token named Memtro with read access, or full access if Memtro may log time, handle approvals or plan.
- 2
The token acts as its user. To read the whole team's time, create it as a user with View All Worklogs. Logging time for others, approving timesheets and planning need that user's Tempo permissions for them.
- 3
In Memtro, open Connections → Tempo and paste the Tempo API token. Set Region to eu or us if you know where your data lives.
- 4
Ask: how many hours were logged on project 10000 last week?
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Tempo tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Tempo?+
Only when you ask, and only what it has been granted: log time against a Jira issue; change a worklog's date, time, hours or description; delete a worklog; submit or recall a timesheet for approval; approve, reject or reopen a timesheet; plan a person or generic resource onto an issue or project; change or delete a plan. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
Who can use a Tempo connection?+
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my Tempo data?+
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect Tempo?+
Tempo API token and optional region. In Jira, open Apps → Tempo → Settings → Data Access → API integration. Create a token named Memtro with read access, or full access if Memtro may log time, handle approvals or plan.
Can Tempo start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Tempo for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Connect Tempo in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.