Timesheets for Jira Cloud whose hours never leave your Atlassian site.
Every other timesheet app for Jira copies your team's hours onto its vendor's servers. That copy is what turns a timesheet into a data-processing question — a DPA to sign, a sub-processor to register, a security questionnaire to fill in, and one more place your employees' working patterns live.
Hourward does not make the copy.
- Time goes into Jira's own worklogs, under the name of the person who typed it. It moves Jira's
own Time spent field, and
worklogAuthor = currentUser()finds it — because it really is theirs. - The app stores no hours, no names, no email addresses. Only whether a week has been submitted and approved, which is the one thing Jira has no place for.
- It declares no permission to send data outside Atlassian. Atlassian verifies this itself: Hourward is in the Runs on Atlassian programme, and Atlassian notifies your administrators if an update ever changed that.
| Log time | from the issue you are on, or from a weekly grid. 1h 30m, 1h30, 90m and 1:30 all work, and the form shows you what it understood before you commit it. |
| Submit a week | and have a manager approve it or send it back with a reason. Nobody can approve their own week, approver or not. |
| A decided week is closed | Hourward's own screens will not write into a submitted or approved week — whichever week the date you pick falls in, not just the one on screen. |
| Report | by person, project, issue or day, over any range, on a dashboard or in the app. |
| Export | a CSV carrying both the account id a payroll system joins on and the name a human checks. |
Jira's own working day and week settings are read from your site, so 1d means what it means to you.
It cannot log time on someone's behalf. No server-side timer, no scheduled import, no bulk migration attributed to a person. Anything written without a person behind it belongs to the app rather than to them, and then disappears from Jira's own worklog searches. That is the defect Hourward exists to avoid, so it is not coming.
It will not switch Jira's time tracking provider for you. Doing that needs Jira administration permission, which Hourward does not ask for. The settings screen tells you where the switch is — and Hourward works perfectly well with Jira's own time tracking left exactly as it is.
If you stop paying, you keep your hours. Atlassian takes the app's screens away when a licence lapses — no app can change that. Every hour stays in Jira's own worklogs, in the tool you already own, because Hourward never had a copy to hand back. No export to run, nobody to ask.
It will not pretend an approved week is unchanged when it is not. Jira lets a worklog be edited at any time and no app can prevent that. Hourward compares the total now against the total claimed at submission, and says when they differ.
On the Atlassian Marketplace — search for Hourward. There is a page describing it, with screenshots, at growingpeas.dev/hourward.
info@growingpeas.dev reaches me, not a queue. Security reports: security@growingpeas.dev.
Alexia, one developer. Growing Peas is the business name on the invoice, not a company behind a support desk.
This repository is the public description of Hourward. The application source is private.