Blog ·

Jira content calendar: plan posts, track reviews, and keep the cadence

A Jira content calendar is a Jira space where every blog post, newsletter, video and social batch is a work item with an owner and a publish date, viewed through the space's calendar view. Give each piece a due date and it lands on the right day of the month grid; move it, and the date moves with it. The weak spot is the cadence. The Tuesday newsletter and the monthly roundup only appear on the calendar once somebody creates them, so this guide sets up the space, the fields and the workflow first, then shows how to make the repeating pieces arrive on their own.

Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation. Atlassian now calls a project a space and an issue a work item; this guide uses both, because most people still search with the older words.

What a content calendar in Jira looks like #

A spreadsheet content calendar has one row per piece and columns for date, channel, owner and status. A Jira content calendar keeps exactly that information, with two things a spreadsheet cannot give you: a status that moves as the work moves, and a link to every comment, draft and approval in one place.

The pieces map like this:

Spreadsheet column Where it lives in Jira
Title of the piece Work item summary
Publish date Due date
Writing starts Start date
Channel (blog, email, social, video) Label
Writer Assignee
Editor or approver A user field, or a mention in the description
Status The workflow status
Brief, outline, links Description
Campaign or theme Parent epic

The due date is the field that matters most, because the calendar view places work by it. A piece with no due date does not appear on the grid at all; it waits in the calendar's Unscheduled work drawer until somebody drags it onto a day.

Set up the space #

One space, one workflow #

Create one space for content, or use the marketing team's space if you have one already. A short workflow covers nearly every format:

Status Meaning
Idea Proposed, not yet committed to a date
Writing The assignee is drafting, filming or designing
In review Waiting on the editor, legal or the product owner
Scheduled Approved and queued in the publishing tool
Published Live

Keep Idea in the workflow even though it looks like backlog. It gives the editorial meeting a single column to review, and an idea that never gets a date simply never leaves it.

Do not add a status per reviewer. A board with Legal review, Brand review and SEO review columns becomes a place where pieces wait without anyone noticing. Put the review steps in the description or in subtasks, and keep one In review column. Our guide to where checklist steps should live covers that trade-off.

Labels for channel, epics for themes #

Label each piece with its channel: blog, newsletter, social, video, podcast. A filter on one label then shows everything in flight for that channel across every theme.

Use an epic for a theme or campaign that spans several pieces, such as a product launch or a quarterly topic. The epic's progress bar answers "how much of the launch content is ready" without a meeting. If your themes have the same shape each time, write the epic once and reuse it; see the Jira epic template guide.

Dates: start date for writing, due date for publishing #

Set the due date to the publish date. Set the start date to when writing begins. On the calendar view, a piece with both dates stretches across the days between them, so a long-form article that takes a week of writing shows as a bar, and a crowded week is visible before it happens.

Use the calendar view as the content calendar #

Open the space and choose Calendar in its navigation (look under More if it is not listed). As of October 2026, Atlassian's calendar view:

Filter the calendar to one label to get a per-channel view. Filter by newsletter and you see every issue of the newsletter for the month; filter by an assignee and a writer sees only their own deadlines.

What the calendar does not do: it holds no events of its own, so a launch date or an industry event that is not a work item will not appear. Create a work item for it, or keep those dates in your shared email calendar. Our Jira team calendar guide covers the view in more depth, including sharing it.

The pieces that repeat #

Most of a content calendar is not campaign content. It is the cadence:

Piece Typical cadence What goes wrong when it is created by hand
Newsletter Weekly, same weekday Created the morning it is due, reviewed in a rush
Social batch for next week Every Friday Skipped in a busy week
Blog post slot Every Tuesday and Thursday The slot exists in someone's head, never on the grid
Monthly roundup First Monday of the month Nobody owns it when the usual writer is away
Podcast or video episode Every two weeks Recording slips because prep never started
Content audit Every quarter Quietly never happens

Every row in that table has the same problem: the calendar view is honest about the work that exists, and this work does not exist until somebody creates it. A calendar that is full for launch week and empty for the routine looks calmer than the month will really be.

How to put repeating content on the calendar #

There are three honest options.

Create by hand Jira Automation scheduled rule A scheduling app
Who creates the piece The editor, every cycle A rule A schedule in the space
"Every Tuesday and Thursday" Whoever remembers A cron expression Pick the weekdays
"First Monday of the month" Whoever remembers A cron expression Pick the weekday position
Due date on each piece Typed each time A smart value in the rule An offset from the run
Cost Time Counts toward your plan's automation usage App licence

Option 1: create by hand #

Keep a template work item per format and clone it at the weekly planning meeting. It costs nothing and it works well for one newsletter and an occasional post. It fails in the week the editor is away, which is usually the week it mattered.

Option 2: a Jira Automation rule #

Jira Automation's Scheduled trigger can create a work item on a timer, either at a fixed rate or on a cron expression. A weekly newsletter is a simple fixed-rate rule. "Tuesday and Thursday" and "first Monday of the month" need cron; our Jira cron expression guide covers the syntax and the schedules it cannot express, and Jira smart values covers setting the due date from the run. Each run counts toward your plan's monthly automation usage, explained in Jira Automation pricing.

Option 3: a scheduling app #

Recurring Work Items for Jira is our app, and repeating work on a schedule is the job it does. For a content calendar:

  1. Turn the app on for the content space.
  2. Set the working week and add public holidays, so a scheduled piece does not land on a day nobody is working.
  3. Create one rule per repeating piece. Schedules can be every N days, chosen weekdays every N weeks, a day of the month, or a weekday position such as the first Monday or the last Friday of the month.
  4. Name each piece with tokens, for example Newsletter {{now.date}}, so every issue has its own title on the calendar.
  5. Set the assignee, the channel label, the description with the brief, and the due date as an offset from the run, so each piece arrives already on the right day of the grid.

It uses no Jira Automation quota, a rule only ever creates work in the one space it lives in, and every run that creates or fails is written to the rule's history with its reason. It is free for up to 10 users.

A starter set of repeating content #

A set most content teams can adopt in the first week:

If you also report on the content each month, the Jira monthly report guide covers the filters, and Jira for marketing covers the wider routine beyond content.

Useful filters for a content calendar #

Save these and subscribe to them so the list arrives by email on planning day. Replace CON with your space key.

  1. Due this week: project = CON AND due <= endOfWeek() AND statusCategory != Done
  2. Stuck in review: project = CON AND status = "In review" AND updated <= -3d
  3. Published last month: project = CON AND status = Published AND resolved >= startOfMonth(-1) AND resolved < startOfMonth()
  4. Ideas with no date: project = CON AND status = Idea AND due is EMPTY

The last one is your editorial meeting's agenda: ideas that need a decision, a date, or a polite close.

When the manual way is enough #

Not every team needs automation here. If you publish one newsletter and a post when there is news, create the pieces by hand at your weekly planning meeting and keep the calendar view open while you do. If you already run a few Automation rules and stay comfortably within your plan's usage, a Scheduled rule for the newsletter is a natural next step. A scheduling app earns its place when the repeating list grows past what anyone wants to maintain as cron expressions, or when the first-Monday and twice-a-week pieces keep landing on the wrong day.

Frequently asked questions #

Can Jira be used as a content calendar? Yes. Make each piece a work item with a due date as the publish date, and use the space's calendar view to see the month. Labels give you a per-channel view.

How do I see only one channel on the Jira calendar? Label each piece with its channel and filter the calendar view by that label.

Can Jira create the weekly newsletter item automatically? Yes, with a Jira Automation Scheduled rule, or with a scheduling app such as Recurring Work Items for Jira, which creates it on the weekday you choose with its own title, assignee and due date.