Blog ·
Jira for legal teams: requests, contracts, and the compliance calendar
Jira for legal teams works best as three things in one project: a front door for requests from the rest of the company, a workflow that moves contracts from draft to signature, and a calendar of recurring obligations that never depends on somebody remembering. The first two are what Atlassian's legal templates are built for. The third is where legal teams get caught out, because a filing, a renewal notice or a policy review comes round on a fixed date and nobody files a request for it. This guide sets up the first two quickly, then spends its time on the third.
Statements about Jira's built-in features are as of October 2026, from Atlassian's own pages.
Why legal teams end up in Jira #
Usually because the rest of the company is already there. Engineering, IT and operations run their work in Jira, so legal requests arrive as comments, emails and chat messages that point at Jira tickets anyway. Bringing legal into the same tool gives the team a queue it can see, a record of who asked for what, and a place to report on workload.
Jira suits legal work that is:
- request driven, such as contract reviews, NDAs and policy questions from other teams;
- made of steps with owners, such as draft, negotiate, approve and sign;
- tied to dates, such as renewals, filings and annual reviews;
- shared with the business at the level of status, while the documents stay in your document system.
It is a weaker fit for storing the contracts themselves, for e-signature, and for matter billing. Keep those in the tools built for them and link out from the ticket.
Start from Atlassian's legal templates #
Atlassian publishes a set of legal templates for Jira. As of October 2026 its legal template page lists three:
| Template | What Atlassian says it is for |
|---|---|
| Project management | "Manage activities for completing a business project." |
| Legal service management | "Manage and track all your contracts and legal requests." |
| IP infringement | "Simplify IP infringement claims from start to finish." |
For most in-house teams, legal service management is the one to start with. It gives you a single project for incoming requests and contracts, which you can then shape to your own stages. The IP infringement template suits a team that handles a steady flow of takedown or infringement claims and wants each one tracked from report to resolution.
Whichever you choose, treat it as a starting point. Rename the statuses to the words your team already uses, remove the fields nobody fills in, and add the one or two that matter to you, such as the counterparty or the contract value band.
Set up the request queue #
The request queue is how the rest of the company reaches you. A few choices make it work:
- Give each request type its own work type or label: contract review, NDA, policy question, data protection question. Reporting by type is how you show where the team's time goes.
- Ask for the essentials up front: the counterparty, the deadline the requester is working to, and a link to the draft. A request with no draft is a conversation, and it can wait for one.
- Assign on intake, even if only to a triage owner. An unassigned request is one everybody assumes somebody else has.
- Keep confidential matters out of the shared queue. Litigation, employment matters and anything privileged belong in a separate project with tighter permissions, not in a queue the whole company can browse.
That fourth point depends on your plan. Atlassian's page on the Free plan says permissions, roles and work-level security are not customisable there, so a legal team that needs restricted projects should plan on a paid plan.
A workflow for contracts #
Contracts move through the same stages again and again, which makes them a good fit for a Jira workflow. A typical one:
| Status | Who acts | Leaves the status when |
|---|---|---|
| Requested | Requester | The draft and details are attached |
| In review | Legal | Comments go back, or it is approved as is |
| Negotiating | Legal and counterparty | Terms are agreed |
| Approval | Signatory or finance | The approver signs off |
| Signature | Both parties | Signed copies are stored |
| Done | Nobody | The renewal date is recorded |
The last row matters more than it looks. When a contract closes, record its renewal date and its notice period on the ticket. That date is the start of the next piece of work, and it is the piece most teams lose.
For contracts that share most of their steps, a subtask checklist on each ticket keeps the steps visible. Our Jira subtask template guide covers four ways to get the same subtasks every time.
The compliance calendar nobody files a request for #
Requests come from people. The recurring obligations come from the calendar, and nobody sends a request for them. Here is a typical in-house routine:
| Obligation | Cadence | What goes wrong without a ticket |
|---|---|---|
| Contract renewal and notice check | Monthly | A notice window passes and the contract renews on old terms |
| Policy review (privacy, acceptable use, code of conduct) | Yearly | The policy quietly goes out of date |
| Data processing register review | Quarterly | New vendors are never added |
| Board or entity filings | Yearly, on a fixed date | Filed late, under pressure |
| Trademark renewal check | Yearly | A mark lapses because the reminder went to a former employee |
| Training and attestation reminders | Yearly | Nobody chases the people who did not complete it |
Each of these is easy to do and easy to forget. They sit in a spreadsheet or in one person's calendar, and when that person is away the date passes. A recurring obligation should create its own ticket, assigned and dated, before the deadline rather than on it.
Three ways to make the calendar create tickets #
| Create by hand | Jira Automation scheduled rule | Recurring Work Items for Jira | |
|---|---|---|---|
| Effort | Every ticket, every cycle | One rule per obligation, written once | One rule per obligation, chosen from a form |
| Schedule | Whoever remembers | Fixed rate or cron expression | Daily, weekly, or monthly on a day or a weekday, every N months |
| Lives in | Somebody's calendar | The automation rules list | The legal project itself |
| When it misses | Nobody knows | Check the rule's audit log | Run history with the reason |
By hand #
Fine for a handful of obligations. Somebody owns a compliance calendar and creates the tickets at the start of each month, ideally by cloning last cycle's. Our Jira task template guide makes those clones quick. The risk is the one above: the calendar has one owner.
Jira Automation #
Jira's own automation can create a work item on a schedule. Atlassian's trigger reference describes running a rule at a fixed rate or with a cron expression for more complex schedules. That covers most legal routines. Two things to plan for: a yearly date on "the first working day of March" is hard or impossible to say in cron, and our Jira cron expression guide covers the gaps; and every run counts toward your plan's monthly automation usage, which Jira Automation pricing explains.
A scheduling app #
Recurring Work Items for Jira is built for this job. Its rules are scoped to one project, so the legal team's calendar lives inside the legal project rather than in a site-wide rules list that other admins edit. A project administrator turns it on for the project, and a rule made there creates work only there.
Set up the compliance calendar with Recurring Work Items #
- Open the legal project and turn the app on for it.
- Create one rule per obligation. A yearly review is a monthly rule repeating every 12 months; a quarterly register review repeats every 3 months.
- Pick the day. "The 15th" or "the last Friday of the month" are both choices in the form.
- Set your working days and holidays, so a rule that would land on a weekend moves to a working day instead.
- Write the title with tokens so each cycle's ticket is distinct, for example
Privacy policy review {{now.year}}. - Fill in the template: the owner, a due date a set number of days after the run, labels, and a description that names the source of the obligation.
- Add subtasks where the obligation has steps, such as pull current policy, collect changes, approve, publish.
Create the ticket early. For a renewal with a 90 day notice window, schedule the check well before the window opens, and put the real deadline in the due date. The ticket's job is to start the work, not to mark the last possible day.
A rule can be given an end, either a date or a number of runs. That suits obligations that stop: a transition period under a new regulation, or a vendor contract you know you will exit.
Every run is recorded in the rule's history as created, skipped or failed, with the reason. When an auditor asks whether last year's policy review was raised, the history and the ticket together answer it.
Report on the legal workload #
A legal team in Jira can finally show its workload instead of describing it. A few saved filters do most of it:
- open requests by type, to show where the time goes;
- requests older than your target, to spot what is stuck;
- this quarter's compliance tickets and their status, for the leadership update.
Our Jira weekly report guide shows how to turn a filter into an emailed summary, which is often all the business needs from legal each week.
When the manual way is enough #
A recurring schedule earns its keep once the calendar is bigger than one person's memory. You probably do not need one if:
- you are a team of one or two with a short list of dates you already track reliably;
- your obligations live in a dedicated compliance tool that already reminds the right people;
- almost all your work is reactive, so the request queue is the whole job.
Once the obligations run into dozens, or the person who holds the calendar is away for a month, a missed date costs more than the setup.
FAQ #
Is there a Jira template for legal teams? Yes. As of October 2026 Atlassian lists legal service management, IP infringement and a general project management template for legal teams.
Should legal use Jira or Jira Service Management? Jira works for an internal team that takes requests from colleagues. A team that wants a request portal for the whole company, with request forms and queues, may prefer Jira Service Management.
Can Jira remind us of contract renewals? Not on its own from a date field. You need a scheduled rule, either in Jira Automation or in an app such as Recurring Work Items for Jira, that creates the renewal check ticket ahead of the notice window.
Can confidential matters stay private? On a paid plan, yes, with a separate project and its own permissions. On the Free plan Atlassian says permissions are not customisable.