Blog ·
Jira for education: courses, school IT, and the academic calendar
Jira for education works well when you treat it as two things at once: a board for the projects a school or university team runs (a new course, a system rollout, an accreditation review) and a calendar of routine work that comes back every term. Jira handles the first out of the box. The second is where most education teams struggle, because the academic year repeats on a rhythm Jira does not know about: term starts, grading deadlines, breaks, and reports that are due on the same date every year. This guide covers who in education uses Jira, how to set up a project for each kind of team, and how to make the term's routine tickets appear on their own.
Who uses Jira in education #
Jira is rarely the tool teachers plan lessons in. It shows up where education looks like any other organisation running projects:
| Team | What they track in Jira | Rhythm |
|---|---|---|
| School or university IT | Device rollouts, account requests, system upgrades | Busiest before each term |
| Learning technology and LMS teams | Course site setup, integrations, support requests | Every term start |
| Curriculum and course design | New courses, revisions, review cycles | Per academic year |
| Research groups | Experiments, papers, grant deliverables | Grant reporting dates |
| Student software projects | Sprints, backlogs, demos | Per semester |
| EdTech product teams | A normal software product | Sprints, with a seasonal peak |
The common thread is the calendar. Every team on that list has work that repeats on the academic year, and most of it is predictable months ahead.
Set up a project for course and curriculum work #
Course design is project work with stages. A board with a few columns fits it better than a request queue.
A workable set of columns:
- Proposed: a course idea or a revision request, with the reason.
- In design: learning outcomes, structure and assessment being written.
- In review: a colleague, a committee or a quality office is reading it.
- Building: the course site, materials and assessments are being produced.
- Ready for term: done, waiting for the term to start.
Make each course an epic and each module or deliverable a task under it. That way the epic shows how close a course is to ready, and the board shows where every module sits. Our Jira epic template guide covers what to put in an epic description so every course starts with the same structure.
Put the term start date in the epic's due date. A filter of epics due in the next six weeks that are not yet in "Ready for term" is the one view a curriculum lead needs in August and in January.
Set up a queue for IT and admin requests #
School IT, the LMS team and administrative offices get requests from staff and students. Those belong in a queue with a priority, not on the same board as planned projects. If you have Jira Service Management, a service project gives you a request portal. If you only have Jira, a simple project with a "Request" type and a triage column works.
Keep three request types apart, because they are answered differently:
- Access and accounts: a new staff member, a student who cannot log in, a role change.
- Course site requests: a new course shell, enrolment problems, an integration that stopped syncing.
- Faults: something broken in a classroom, a lab or a system.
Our Jira for IT operations guide covers the split between the request queue and planned work in more depth, and most of it carries over to a school or university IT team unchanged.
The academic calendar: work that comes back every term #
This is the part most education teams run from memory or a shared spreadsheet. A typical year contains routine work like this:
| Routine | When | Usually owned by |
|---|---|---|
| Course sites created for next term | Six weeks before term | LMS team |
| Classroom and lab equipment check | Two weeks before term | IT |
| Account clean-up for leavers | After each term ends | IT |
| Grade submission reminder and check | Before each grading deadline | Registry or faculty office |
| Course evaluations opened | Last weeks of each term | Quality office |
| Curriculum review | Once a year | Curriculum committee |
| Accreditation or compliance report | Fixed date each year | Quality or compliance lead |
| Software licence renewals | On each renewal date | IT |
| Backup restore test | Monthly | IT |
Every one of these is predictable, and every one is forgotten at least once when the person who usually remembers is away. A routine that only exists in someone's head is not a process. It becomes one when it is a ticket that appears on time, with an owner and a due date.
Terms are not months #
The awkward part is that the academic calendar does not map neatly onto a monthly or weekly schedule. A few patterns cover most of it:
- Every N months: a routine tied to a semester can run every six months; one tied to a trimester runs every four.
- A weekday position: "the first Monday of the month" for a monthly staff check, or "the last Friday" for a report.
- A fixed day of the month: licence renewals and monthly checks.
- Once a year: every twelve months, for accreditation and annual reviews.
Breaks and holidays matter more in education than almost anywhere else. A ticket that appears on the first day of a two-week break is a ticket nobody reads until it is late. Whatever creates your routine tickets should know your term breaks and public holidays.
How to create the term's routine tickets automatically #
There are three practical ways to get these tickets created on schedule.
| Clone by hand | Jira Automation scheduled rule | A scheduling app | |
|---|---|---|---|
| Who creates the ticket | A person, every time | A rule | A rule in the project |
| "Every six months" or "first Monday" | Whoever remembers | Fixed rate or a cron expression | Chosen in the form |
| Term breaks and holidays | Whoever notices | Up to the rule's logic | Set once for the project |
| Subtasks created with it | Cloned with the ticket | Extra rule actions | Part of the rule |
| Cost | Staff time | Counts toward your plan's automation usage | App licence |
Clone by hand #
Keep last term's ticket as a model and clone it. This is free and fine for one or two routines owned by someone dependable. It fails in the term that person is on leave or has moved jobs, which in education happens every summer.
Jira Automation #
As of October 2026, Atlassian's trigger reference says the Scheduled trigger can "run the flow at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules." Weekday positions and anything tied to a calendar need cron, and our Jira cron expression guide covers the syntax and the schedules cron cannot express. Each run counts toward your plan's automation usage, which Jira Automation pricing explains. Holidays and breaks are not part of a cron expression, so a rule that should skip a break needs extra logic or a person to pause it.
A scheduling app #
Recurring Work Items for Jira is our app, and a calendar of routine work is the job it was built for. For an education team:
- Turn the app on for the project, and choose who may schedule.
- Set the working week and add your term breaks and public holidays as holidays. Then, in each rule, choose Move it to the next working day under If it falls on a non-working day, so a run that lands on a day off moves to a working day: a new rule runs on the day it falls on, holiday or not.
- Create a rule per routine: every six months for a semester task, a weekday position such as the first Monday for a monthly check, or every twelve months for an annual report.
- Title it with tokens so each ticket names its period, for example
Course sites for next term, {{now.monthName}} {{now.year}}. - Add the checklist as subtasks, an assignee, labels, and a due date as an offset from the run.
A rule can be paused and resumed, and it can end after a number of runs or on a date, which suits a routine that only exists for one grant or one programme. It uses no Jira Automation quota, because the scheduling is the app's own. Each run is written to the rule's history, including the ones that failed and why. A rule only creates tickets in the project it lives in, so the IT routine stays in the IT project and the curriculum review stays with the curriculum team. It is free for up to 10 users.
A starter set of recurring education rules #
| Rule | Schedule | Due | Subtasks |
|---|---|---|---|
| Course sites for next term | Every 6 months, six weeks before term | Two weeks after creation | Create shells, copy content, enrol staff |
| Pre-term equipment check | Every 6 months, two weeks before term | Term start | Classrooms, labs, loan devices |
| Leaver account clean-up | Every 6 months, after term ends | Two weeks after creation | Staff, students, shared drives |
| Grade submission check | Before each grading deadline | The deadline | One per department |
| Licence renewal review | Monthly, first Monday | End of month | One per renewal due |
| Backup restore test | Monthly, last Friday | Same week | Restore, verify, record |
| Annual curriculum review | Every 12 months | Six weeks after creation | One per programme |
Start with the two or three that were late last year. A short list that runs every term is worth more than a long one nobody trusts.
Reporting for heads of department and auditors #
Three saved filters answer most questions. Replace EDU with your project key.
- What is due before term starts?
project = EDU AND due <= endOfMonth(1) AND statusCategory != Done ORDER BY due ASC - Did every routine happen this year?
project = EDU AND labels = routine AND resolved >= startOfYear() ORDER BY resolved ASC - What is overdue?
project = EDU AND due < now() AND statusCategory != Done
Subscribe the department head to the third filter weekly. The Jira weekly report guide shows how to turn filters like these into a short email.
When the manual way is enough #
If one person owns two or three routines and has never missed one, a calendar reminder and a cloned ticket are enough. A schedule earns its place when routines are shared across people, when staff change between years, when term breaks keep shifting the dates, or when an accreditation body wants to see that a review happened every year.
Student teams running a single-semester software project rarely need recurring tickets at all. A sprint board and a retrospective template cover them.
Frequently asked questions #
Is Jira used in education? Yes, mostly by school and university IT, learning technology teams, curriculum and quality offices, research groups and student software projects. It is less common for day-to-day lesson planning.
How do I schedule tasks around the academic year in Jira? Make each routine a recurring ticket with an owner and a due date. Use a schedule of every six months for semester work and every twelve for annual work, and make sure whatever creates the tickets knows your term breaks.
Can Jira skip school holidays? A Jira Automation cron schedule does not know your holidays. Recurring Work Items for Jira lets you list them once for the project, and a rule set to Move it to the next working day under If it falls on a non-working day moves a run that lands on one to a working day. Without that choice, a new rule runs on the day it falls on, holiday or not.