Blog ·
Jira for marketing: a board that keeps the routine work coming
Jira for marketing works best when you keep it smaller than the software teams around you would. One project for the team, a workflow of four or five statuses, campaigns as epics, and each deliverable as a task with an owner and a due date. The part most marketing teams underestimate is the routine: the newsletter every Tuesday, the social calendar every Friday, the monthly performance report, the quarterly content audit. That work comes back on a clock, and a board only shows it if somebody remembers to create the ticket. This guide sets up the project first, then makes the routine appear on its own.
Statements about Jira's built-in features are as of September 2026, from Atlassian's own documentation.
Why marketing teams end up in Jira #
Usually because the rest of the company is already there. Engineering ships in Jira, product plans in Jira, and a launch needs the landing page, the release notes and the announcement email to move together. When marketing tracks its half somewhere else, somebody spends every launch copying status between two tools.
Jira is a good fit for marketing work that is:
- made of deliverables with owners, such as a blog post, an ad set or a webinar deck;
- reviewed before it ships, so a status like In review means something;
- tied to other teams' dates, like a product launch or a sales kickoff;
- repeated on a schedule, which is where most of the hidden work lives.
It is a weaker fit for pure brainstorming and for long-form writing itself. Keep drafts in your docs tool and link them from the ticket.
Set up the project #
One project, a short workflow #
Create one project for the marketing team. A board with these columns covers nearly every marketing deliverable:
| Status | What it means | Who moves it |
|---|---|---|
| To do | Agreed, not started | Anyone planning the week |
| In progress | Somebody is writing, designing or building it | The assignee |
| In review | Waiting on an approver: brand, legal, product | The assignee |
| Scheduled | Approved and queued to publish on a date | The assignee |
| Done | Published or sent | The assignee |
Resist adding a status for every hand-off. A column that nobody moves cards out of becomes a place where work hides. If legal review needs tracking, a label or a checklist inside the ticket is usually enough.
Campaigns as epics, deliverables as tasks #
A campaign is a set of deliverables that share a goal and a date, which is exactly what an epic is. "Spring launch" becomes the epic. The landing page, the three emails, the paid social set and the launch blog post are tasks under it. The epic's progress bar then answers the question a manager actually asks: how much of the launch is ready?
If your campaigns have the same shape every time, write the epic once and reuse it. Our Jira epic template guide covers what belongs in one, and Jira subtask template covers the repeated steps inside a single deliverable.
Labels for channel, components for nothing #
Use labels for the channel (email, social, paid, seo, events) so a filter can pull every email in flight across campaigns. Most marketing teams do not need components; labels are faster to add and easier to change when the channel mix moves.
The routine work nobody creates a ticket for #
Launches get tickets because they are exciting. The routine does not, because it is the same every time. Look at a typical marketing month:
| Routine | Cadence | What goes wrong without a ticket |
|---|---|---|
| Newsletter | Every week, same weekday | Drafted late, reviewed in a rush |
| Social calendar for next week | Every Friday | Skipped in a busy week, nobody notices until Monday |
| Performance report | First working day of the month | Written from memory, no owner when the usual author is away |
| Paid campaign budget check | Every two weeks | Overspend spotted after the fact |
| Content audit | Every quarter | Quietly never happens |
| Event and webinar follow-up | After every event | Leads go cold |
The last row is triggered by an event rather than a clock, so it belongs in your event epic template. Every other row is a recurring ticket, and treating it as one gives it the same owner, due date and visibility as the launch work beside it.
How to create recurring marketing tickets in Jira #
There are three honest options, and the right one depends on how many rules you need and who will maintain them.
| Clone by hand | Jira Automation scheduled rule | A scheduling app | |
|---|---|---|---|
| Who creates the ticket | A person, every cycle | A rule | A schedule in the project |
| Setup | None | A rule per routine | A rule per routine, in a form |
| "First working day of the month" | Whoever remembers | Needs a cron expression | Chosen in the form |
| What happens when someone is away | The ticket is not created | Created on time | Created on time |
| Cost | Time | Counts toward your plan's automation usage | App licence |
Option 1: clone by hand #
Keep one "master" ticket per routine and clone it each cycle. It costs nothing, and for a team of two with one weekly newsletter it is fine. It fails in exactly the week you are busiest, and it depends on one person's memory.
Option 2: a Jira Automation rule #
Jira Automation's Scheduled trigger creates a work item on a timer. Atlassian's trigger reference, as of September 2026, says you can "run the flow at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules." That covers the weekly newsletter easily. Monthly and quarterly routines need a cron expression; our Jira cron expression guide covers the syntax and the schedules it cannot express. Each run counts toward your plan's monthly automation usage, explained in Jira Automation pricing. The same Atlassian page notes that "Scheduled flows that reach a Failure status for 10 consecutive executions will disable automatically," so check a rule's audit log now and then.
Option 3: a scheduling app #
Recurring Work Items for Jira is our app, and it is built for this job. A marketing routine becomes a rule in the project:
- Turn the app on for the marketing project and choose who may schedule.
- Set the working week and add public holidays, so a rule can move off a day the team is not working.
- Create a rule for each routine. The schedule options are 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.
- Write the title with tokens so each ticket has its own name, for example
Newsletter {{now.date}}. - Put the checklist in the description, set the assignee, the labels and the due date as an offset from the run.
It uses no Jira Automation quota, and every run, whether it created, skipped or failed, is written to the rule's history with its reason. A rule is scoped to the one project it lives in, so the marketing team's schedules never create tickets anywhere else. It is free for up to 10 users.
A starter set of recurring marketing rules #
A set most teams can adopt on day one:
- Weekly newsletter, every Monday, due Tuesday. Description: subject line, lead story, links, review by, send time.
- Social calendar for next week, every Friday, due the same day.
- Monthly performance report, on the first Monday of the month. Description: the saved filters or dashboards to read, and headings for What worked, What did not, Next month. The Jira weekly report guide shows how to build those filters.
- Paid budget check, every second Wednesday.
- Quarterly content audit, every three months on the 1st, with a checklist: find pages with outdated dates or prices, merge thin posts, update internal links.
If a routine has several fixed steps that different people own, put them in subtasks rather than one long description. See where checklist steps should live for the trade-offs.
Reporting on marketing work #
Once the routine is on the board, Jira can answer questions that used to need a meeting:
- What is due this week?
project = MKT AND due <= endOfWeek() AND statusCategory != Done - What did we ship last month?
project = MKT AND resolved >= startOfMonth(-1) AND resolved < startOfMonth() - What is stuck in review?
project = MKT AND status = "In review" AND updated <= -3d
Replace MKT with your project key. Save each as a filter and add a filter subscription so the list arrives by email on the day you plan.
When the manual way is enough #
Not every marketing team needs any of this. If you have one or two recurring routines and one person who owns them reliably, clone by hand and keep a calendar reminder. If your team already runs a handful of Automation rules and stays comfortably inside your plan's usage, a Scheduled rule for the newsletter is the natural next step. A scheduling app earns its place when the routine list grows past what anyone wants to maintain as cron expressions, or when schedules like "first working day of the month" keep going wrong.
Frequently asked questions #
Is Jira good for marketing teams? Yes, for deliverable-based work with reviews and deadlines, especially when the rest of the company already uses Jira. Keep the workflow short and drafts in your docs tool.
How do I plan a campaign in Jira? Make the campaign an epic and each deliverable a task under it, with a label for the channel and a due date that works back from the launch.
Can Jira create the weekly newsletter ticket 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.