Jira for marketing teams. How to plan campaigns, manage requests, and turn customer insights into action?

When it comes to Jira for marketing teams, most organizations fail because work is fragmented. And when tasks are scattered across five different apps, it’s impossible to tell which efforts are actually driving results. 

You know the situation. Your briefs are in Confluence, the tasks are in Jira, and feedback is in Slack. At the same time, insights are trapped in Looms and DMs. This results in chaos. Instead of shipping work, the marketing team spends the day playing detective: searching, chasing, and rebuilding context.

This is why this guide shows you how to make Jira the home base for your marketing. 

We’ll walk through how to plan campaigns, get on the same page as sales, and use Rovo to finally hit the KPIs and goals that matter.

Marketing teams usually start with lightweight tools because the work feels creative, fluid, and hard to standardize.

That works for a while.

Then the team grows. Campaigns multiply. Sales asks for more enablement. Product launches require more coordination. Designers get overloaded. Leadership wants visibility. Content requests come from every direction. Demand generation needs to show pipeline impact. Events need deadlines, vendors, deliverables, and stakeholder approvals. Suddenly, “just put it in Slack” stops working.

Atlassian describes marketing project management as a way to plan campaigns, execute them efficiently, and measure business impact. Jira supports that through visual boards, workflows, timelines, dashboards, reports, automation, forms, approvals, and integrations.

For marketing, this matters because the team needs to answer questions like:

The goal is s to give creative, strategic, and operational work enough structure so people can move without constantly asking for status updates.

Atlassian’s lesson on setting up Jira for marketing teams is practical. It starts with the team’s real way of working.

The key idea: you do not need to change your process to match Jira. Instead, space admins can configure team-managed business spaces to support the way the team already works. Atlassian uses two examples: an events marketing team and a demand generation team. Events marketing needs to track many contributors and event details. Demand generation needs to plan campaigns, communicate timelines and results, and collaborate with many teams.

That is a useful starting point for any marketing team. Before configuring Jira, decide what type of marketing work you want to manage.

For events teams, Atlassian’s example uses epics for major workstreams at large events, such as breakout sessions, keynote addresses, or training sessions. Tasks represent smaller pieces of work, such as confirming a keynote speaker, vetting a caterer, or touring a venue. The team also creates custom work types: deliverable, major milestone, and meeting.

That gives event teams a clear structure:

This is easy enough for non-technical teams, but structured enough to keep an event from turning into a spreadsheet, a Slack channel, and a pile of reminders.

Demand generation teams need a slightly different setup. They often manage multiple campaigns simultaneously across channels, personas, funnel stages, and business goals.

A useful structure could look like this:

Last but not least, start simple and add customizations when the team sees what would be helpful. Too many fields and issue types at the beginning can make Jira feel like extra work instead of a shared workspace. 

A marketing workflow should show the real path from idea to done.

This is why event marketing example uses a simple workflow: To Do, In Progress, In Review, Blocked, Canceled, and Done. The board mirrors those statuses so the team can quickly understand what is happening.

For many marketing teams, that basic workflow is enough for general tasks. However, for campaigns, content, and creative work, you may need more specific workflow stages.

A content workflow could look like this:

This gives the team more than a “done/not done” view. It shows where work gets stuck.

A campaign workflow could look like this:

The key is the handoff between the campaign launch and Sales follow-up. Many campaigns technically launch, but the Sales team does not know what to do next. That creates the classic gap: Marketing delivers the asset, Sales misses the moment, and leadership wonders why the campaign did not influence the pipeline.

Note that a strong Jira workflow makes the follow-up plan part of the campaign.

Marketing work is cross-functional by default. A single campaign may involve demand generation, content, product marketing, design, web, RevOps, Sales, leadership, and sometimes legal or finance.

That does not mean everyone should have the same permissions.

Use default and custom roles: Administrator, Member, Contributor, and Viewer. Administrators manage the space. Members own workstreams. Contributors can edit, update, and collaborate, but may not create or delete work items. Viewers can follow progress without changing the work.

For marketing, this kind of role setup helps prevent two common problems:

First, stakeholders cannot accidentally rewrite the team’s board every time they want an update.

Second, contributors can still collaborate without everything having to flow through the project owner.

A practical marketing setup could look like this:

This setup keeps Jira open enough for collaboration, but controlled enough to avoid accidental process changes.

A healthy Jira setup for marketing should cover three levels of work.

This includes annual priorities, quarterly goals, major launches, brand campaigns, market expansion, customer retention, and revenue goals.

In Jira, this can be represented through goals, plans, epics, campaigns, or initiatives, depending on your Atlassian setup.

The key is that strategic work should answer the question: why are we doing this?

This is the visible layer of marketing execution:

This is where boards, timelines, assignees, dependencies, and due dates matter most.

This includes requests from Sales, Product, Customer Success, leadership, and other teams.

Examples:

Without structured intake, these requests arrive through Slack, email, meetings, and hallway conversations. That makes marketing look reactive, even when the team is doing strategic work.

This is where Jira Service Management becomes valuable.

A marketing service desk can become the front door for campaign and content requests.

The problem it solves is familiar: Marketing and Sales lose alignment because requests arrive reactively, often as “let’s do a webinar” or “we need a one-pager,” without a clear business reason. That leads to vanity projects, scattered operational tasks, and content that does not support a specific funnel stage. 

The solution is a structured Demand Generation Service Desk that centralizes campaign and content intake. Requesters must define strategic goals upfront, such as New Logos or Churn Prevention, so every initiative is connected to measurable value. The system can process strategic requests with personas and ROI targets, map assets to funnel stages, identify gaps, route design work to the right specialists, and enforce stakeholder approvals.

That changes the role of Marketing.

Instead of being an order-taking team, Marketing becomes a strategic execution team. Each campaign has a defined budget, target audience, business goal, and follow-up plan. Content is balanced across the funnel. Sales is aligned because the handoff is required. 

A good marketing request form should ask:

That last question matters. Without it, Marketing cannot prioritize. Everything feels urgent because nothing is tied to a measurable value.

Jira gives structure to work. Rovo helps teams use the knowledge around that work. You can break this into three simple capabilities:

Find: Search across tools like Drive, SharePoint, and Jira from one place.
Learn: Ask questions about the information, such as “Summarize the key decisions from this Loom video.”
Act: Use specialized AI agents to perform scoped jobs, such as reviewing calls, creating tickets, drafting summaries, or flagging messages.

Rovo Agents are specialized AI agents that support project tracking, ticket responses, incident briefings, and custom agent workflows. 

Rovo Studio allows teams to build agents, automations, hubs, and assets, including custom agents with unique knowledge, actions, and external tools.

When it comes to the real use cases for marketing, Rovo can help with work like:

Marketing needs to understand why deals stall, why opportunities go Closed Lost, what prospects say about pricing, and what content would help Sales move deals forward. But Sales rarely fills in the “Lost Deal” field with enough detail. The real reasons are often trapped in calls and people’s heads.

The solution is a specialized Rovo Agent for Marketing connected to:

The agent can answer questions like:

The impact is a weekly, evidence-based objections report without forcing Marketing to schedule another meeting with Sales. Messaging and content priorities are based on what prospects actually say on calls.

The Rovo playbook outlines a simple weekly workflow.

First, Marketing runs the Rovo Agent weekly with a prompt such as: “Review Loom videos from last week for deals in stage Evaluation. Summarize the top 3 recurring objections about pricing vs Competitor X.”

Then Rovo scans Loom transcripts in the defined folder and extracts patterns like:

It also pulls short quotes as evidence.

Next, Rovo outputs a weekly Voice of the Customer report with:

If content is missing, Rovo generates a Content Gap Brief with persona, deal stage, objection, suggested outline, and priority.

Finally, Marketing closes the loop by updating messaging docs and decks in Confluence, creating new assets or Jira tickets, and sharing a refreshed “what to send” guide back to Sales.

Use this prompt as a starting point:

It creates a repeatable content intelligence process.

There is a difference between “Sales says pricing is a problem” and “Here are the top three pricing objections. We have exact quotes, recommended messaging, existing assets, content gaps, and next actions”. 

The second option truly helps you plan your Marketing activities based on customer Sales calls.  

Here are the three examples of what you can get out of the Rovo report when it’s set up the way we recommend: 

Objection 1: “Competitor X is cheaper for the same outcome.”

Frequency: high.
Evidence: “We can get similar coverage for less with Competitor X.”
Messaging angle: shift the conversation from sticker price to total cost of ownership and time saved.
Best assets: ROI worksheet, comparison slide, short proof point story.
Content gap: a one-page “TCO and ROI vs Competitor X” handout for internal champions.

Objection 2: “Your pricing model is confusing.”

Frequency: medium.
Evidence: “I do not understand what is included vs add-ons.”
Messaging angle: simplify pricing tiers with two concrete examples.
Best assets: pricing explainer deck section and FAQ page.
Content gap: a “Pricing explained in 60 seconds” Loom clip plus FAQ page.

Objection 3: “Hard to justify internally.”

Frequency: medium.
Evidence: “I need something to convince Finance and my VP.”
Messaging angle: build a champion enablement pack with a clean narrative.
Best assets: internal pitch deck, email template, benefits checklist.
Content gap: an approval kit with a one-pager, email, and slide.

The recommended next actions are clear:

The second major Marketing use case is cross-functional.

Sales reps often spend hours digging for content or sending Slack messages like, “Do we have a deck for X?” Meanwhile, Marketing lacks visibility into which assets are missing in the field.

That creates frustration on both sides.

Sales feels unsupported because they cannot find the right content fast enough.

Marketing feels reactive because requests arrive without context.

A Rovo Agent called “Sales Content Matchmaker” solves this by sitting between Sales calls in Loom and the content library in Confluence or Google Drive. The agent answers questions like:

The impact is two-sided. Sales follow up faster with client-ready assets. Marketing gets a steady stream of real content gap signals from the field, with context from actual calls. The content roadmap becomes driven by deal reality.

The workflow is simple:

This solves three common problems:

For a prospect concerned about security, migration risk, and ROI, the agent could recommend:

The suggested send order could be:

Sales also gets a message they can paste into the follow-up email:

Based on our discussion, these materials cover security, migration risk, and ROI. I suggest starting with the security overview and short clip, then the migration checklist, then the ROI worksheet.

That removes the “what should I send?” delay after a call.

The real value lies in what happens when the agent cannot find a good match.

For example, a missing asset is about data residency and vendor risk for EU teams. The prospect quote is: “We cannot store customer data outside the EU”. The persona is the Ops lead. The deal stage is late evaluation. The recommended asset is a one-page FAQ plus a three-minute explainer clip. The outline includes key points, proof points, what to ask legal, and next steps. The priority is high.

The agent then creates a Jira issue called Content Request, adds the response into the ticket, and posts a Slack message to #marketing-intake with a summary and link to the Jira issue.

Marketing gets a request that already includes:

That is much easier to triage than “Can we get a one-pager about EU data”?

When set up right, Rovo is the intelligence layer across the Atlassian System of Work.

For marketing, the system looks like this:

In this model:

This is close to Atlassian’s current Teamwork Collection marketing positioning. Atlassian describes Jira, Confluence, Loom, and Rovo as one system that connects work, teammates, and knowledge. 

Atlassian highlights staying in sync from kickoff to launch with Loom videos, Confluence strategy docs, Jira progress updates, and Rovo, which helps teams work faster with context.

Rovo can create significant value for marketing teams, but enabling it is not just a user action. It requires setup, guardrails, and data readiness.

Marketing promise: users find decks and contracts.
Hidden IT work: IT must enable Domain-Wide Delegation in Google Admin and connect the Drive connector.
Guardrail: admins can use blocklists and limit scope to specific folders or shared drives.
Limitation: Rovo respects current Drive permissions, so a document that is accidentally public to the organization can become visible through Rovo.

Marketing promise: teams search the official knowledge base without leaving Atlassian.
Hidden IT work: IT must register an app in Microsoft Entra ID and grant Microsoft Graph permissions.
Guardrail: IT should select which sites and libraries to index and exclude confidential data.
Limitation: SharePoint access rules are inherited. Rovo does not fix broken permissions in the source system.

Marketing promise: Slack knowledge becomes searchable, so people can find where and when something was said.
Setup: an org admin connects the Slack workspace in Atlassian Admin and authorizes Slack. End users may need to connect their Slack account.
Guardrail: index only approved channels. Private areas stay private and permission-based.

Marketing promise: teams can search HubSpot deals linked in Atlassian pages through Smart Links.
Setup: when users first see a HubSpot Smart Link in an Atlassian app, they connect through OAuth.
Guardrail and limitation: HubSpot Smart Link search supports Deals, not Contacts, and results appear only when the Smart Link is on a page the user has viewed and the user has access to in HubSpot.

Marketing promise: the account and opportunity context appear where work happens.
Setup: users connect to Salesforce through OAuth when they first open a Smart Link, and a Salesforce admin approves connected app access.
Guardrail and limitation: Salesforce object and field permissions apply, and Rovo focuses on linked objects rather than a full CRM crawl.

Marketing promise: teams can search calls by topic, use transcripts and summaries, and jump to the exact moment in the recording.
Setup: IT links the Loom workspace in Atlassian Admin. Users connect through Smart Links.
Guardrail: Loom visibility rules apply, so internal or space-restricted videos remain governed by Loom permissions.

Marketing promise: users can search their inbox for threads, decisions, and approvals next to Confluence knowledge.
Setup: an admin adds the Gmail connector in Atlassian Admin and authorizes it in Google Admin using Domain-Wide Delegation.
Guardrail and limitation: Gmail is search-only. Email content is not ingested or stored by Atlassian; users only see emails they sent or received, and attachments are not available.

The takeaway: do not sell Rovo internally as “turn it on and magic happens.” The better message is: Rovo can be powerful when you connect the right sources, respect permissions, and clean up the knowledge base first.

AI does not fix messy marketing operations.

If your campaign docs are outdated, Rovo may surface outdated information. When your Loom recordings are named “Recording Jan 12,” the agent may struggle to understand which client, stage, or topic the video relates to. On the other hand, if your CRM has empty fields and no links to transcripts, the agent has little context to analyze.

The Rovo playbook outlines three practical data-readiness principles:

Move outdated drafts to an archive. Tag approved documents with a status such as “Final”.  This helps Rovo cite the current source of truth rather than surfacing legacy content. 

For marketing, this means archiving old decks, outdated messaging docs, past campaign drafts, and retired enablement content.

A practical structure could be:

The agent should not treat every draft as equal to the approved version.

Apply consistent naming conventions to files and recordings. Use patterns like Client – Stage – Date to help Rovo distinguish a discovery call from a closing call.

For Sales and Marketing workflows, use a naming convention such as:

Client Name – Deal Stage – Topic – Date

Acme Corp – Evaluation – Pricing Objections – 2026-04-21

This helps the VoC Reporter and Content Matchmaker understand the business context around each call.

Use clear headings, lists, and tables for important information. Do not bury critical rules, value propositions, pricing explanations, or competitor points inside long paragraphs.

For marketing docs, this could mean using headings like:

[Primary persona]

[Main pain points]

[Approved messaging]

[Proof points]

[Objection handling]

[Competitor comparison]

[Client-shareable assets]

[Internal-only notes]

A clear structure helps Rovo retrieve precise answers rather than broad summaries.

A common marketing problem: insights are trapped in empty CRM fields or unstructured notes. The target state is linked transcripts, where video transcripts are generated and pasted or linked into CRM opportunity fields. The success metric is that the agent can analyze transcripts to identify recurring objections and content gaps. The beneficiary agent is the VoC Reporter, and the technical enabler is Jira Automation.

In practice, this means every important sales call should have:

Without that, Marketing gets fragments. With it, Marketing gets patterns.

A good rollout starts with organizing the way your team works. 

Start by listing where work currently enters the team:

Then classify each request type.

Ask:

This gives you the foundation for Jira work types and JSM request types.

Create the Jira space around your marketing operating model.

Start with:

Keep the first version simple. Atlassian’s recommendation to start with simple fields is important here. The more complicated the first setup is, the harder adoption becomes.

Set up Jira Service Management request types for:

Connect Slack so people can start requests from the tool they already use, but make Jira the place where requests are captured, tracked, and reported.

Before enabling Rovo agents, clean the sources they will use.

Archive outdated docs. Mark approved messaging. Organize client-shareable assets. Rename Loom recordings. Make sure content libraries are structured by persona, funnel stage, use case, industry, and objection.

Start with a weekly VoC Reporter.

Scope it tightly:

Output one report each week.

Measure:

Once the content library is clean enough, launch the Sales Content Matchmaker.

Measure:

Do not treat the setup as final.

Marketing work changes. Campaign priorities change. Sales objections change. Product messaging changes. Your Jira workflows, request types, Confluence docs, and Rovo instructions should evolve with them.

Rovo is most useful when your marketing system already has some structure.

Wait before adding agents if:

In those cases, start with Jira and Confluence hygiene first.

The right order is:

This mirrors the broader lesson from the Rovo playbook: AI value depends on the quality of the source, permissions, and data readiness.

Used well, Jira for marketing teams becomes the operating system. People can use it for campaign planning, content production, stakeholder approvals, Sales requests, launch tracking, reporting, and cross-functional handoffs.

But the bigger opportunity is what happens when Jira is connected to the rest of the Atlassian System of Work.

Confluence keeps the strategy and knowledge. Loom captures context. Jira tracks the work. Jira Service Management structures intake. Slack keeps people informed. Rovo helps teams find, understand, and act on knowledge across the stack.

That is where marketing work changes.

Campaign requests become clearer. Sales follow-ups happen faster. Content gaps come with evidence. Messaging updates are based on real customer language. Marketing stops guessing what Sales needs and starts seeing patterns from the field.

The team still makes the decisions. Rovo just removes the drag around finding, summarizing, connecting, and turning scattered context into structured work.

That is what marketing teams need most: not more tools, but a better system for turning ideas, insights, and requests into work that actually moves the business forward.