Jira actual hours, not a Jira replacement
MarginLayer is a commercial layer: contract → actual hours → scope change in money → invoice readiness. Tasks stay in Jira. In v1 actuals for a project key are one shot; there is no weekly re-sync of the same key. This page is not for Solo: Solo is CSV only.
What stays in Jira
- Tasks, sprints, and worklogs.
- Team workflow and delivery ownership.
What MarginLayer adds
- Commercial baseline and scope-change money status.
- Weekly margin-risk and invoice-ready view.
Other Start+ hour sources: Yandex Tracker · YouTrack · GitLab · Bitrix24
IT outsourcing use case · Do tasks move, or does the tracker stay? · Timetta vs MarginLayer · Pilot package
Looking for a Jira replacement?
If you need one system instead of the tracker, look at PSA, including Timetta Lite. If you need the path to invoice on live T&M while tasks stay in Jira, you need a layer: actual hours are read, the weekly contour is invoice-readiness. MarginLayer does not replace Jira.
Does MarginLayer replace Jira?
No. Tasks, sprints, and worklogs stay in Jira. MarginLayer reads actual hours and adds weekly invoice readiness.
Do we have to migrate tasks?
No. Task migration is not required. On a pilot, actual hours come one-way from Jira or CSV.