Blog ·
Jira for sales: deal support, the pipeline, and the weekly rhythm
Jira for sales works when you give it the jobs it is good at: requests that need another team, deals that move through a few clear stages, and the routine that comes back every week, month and quarter. It should not replace a CRM. If your company already runs one, keep contacts, deals and email history there and use Jira for the work around the deal: the security questionnaire, the custom demo, the pricing approval, the Monday pipeline review. If you have no CRM yet, Jira's lead tracking template is a reasonable start for a small team. This guide covers both, then makes the recurring sales work appear on the board by itself.
Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation.
Where Jira fits in a sales team, and where it does not #
Most sales teams that end up in Jira do so because the people they depend on already live there. A deal needs a solutions engineer for the demo, a product manager for the roadmap question, legal for the redlines and finance for a non-standard discount. Each of those is a request with an owner, a due date and a status, which is what a Jira ticket is.
| Job | Jira | A CRM |
|---|---|---|
| Contacts, accounts, email history | Weak | Built for it |
| Deal stages and forecast amounts | Possible with custom fields | Built for it |
| Requests to engineering, legal, finance | Strong | Usually weak |
| Approvals with an audit trail | Strong | Varies |
| Recurring internal routine | Strong, with a schedule | Reminders per record |
The honest split is: deals in the CRM, deal work in Jira. A team of three founders selling their first contracts can run the pipeline in Jira too, and the next section shows how. Once you have a dozen reps and a forecast someone is held to, a CRM earns its place.
Option 1: a lead board for a team without a CRM #
Atlassian ships a template for exactly this. Its sales guide says:
The lead tracking space template helps your sales team track leads through to closing.
The same page describes creating a work item for each opportunity and tracking "who's been contacted, who's in negotiations, and which opportunities have been won and lost." It also suggests the Due date field for follow-ups:
Use the Due date field to let your team know when they should follow up on a lead you've already contacted.
To make it fit a real process:
- Keep the stages few. New, Contacted, Demo, Proposal, Negotiation, Won, Lost covers most small B2B sales. Every extra column is a place a deal can sit unnoticed.
- Add the fields you will actually filter on. Deal value, close month, source, and the decision maker. Atlassian's guide suggests custom fields for contacts like "the decision maker, or technical contact."
- Use the due date for the next step only. The due date answers "when do I touch this deal next", not "when will it close". Put the expected close date in its own field.
- Make Lost a status with a reason. A required "Lost reason" field turns the board into data for the quarterly review.
This works for a pipeline of a few dozen live deals. It gets awkward when you need email logging, sequences or forecast roll-ups by rep, and that is the signal to move the pipeline into a CRM and keep Jira for the next option.
Option 2: Jira for deal support requests #
This is where Jira helps a sales team most, even one with an excellent CRM. Create one project, often called Sales requests or Deal desk, that the rest of the company works from.
| Request type | Typical owner | What the ticket needs |
|---|---|---|
| Security questionnaire | Security or engineering | The file, the deal, the due date |
| Custom demo | Solutions engineer | Audience, use case, date of the call |
| Pricing or discount approval | Finance or sales leadership | Amount, term, justification |
| Contract redlines | Legal | Draft, the clauses in question, deadline |
| Product question | Product manager | The exact question, who asked, deal size |
Give each request type its own work type or a request form, so the person filling it in is asked for what the owner needs. Put the CRM deal link in a field on every ticket so nobody has to search for the account. Approvals belong in the workflow: a ticket that cannot move to Approved without the right person is a better record than a thumbs-up in chat. Our Jira workflow examples include an approval flow you can copy.
The rule that keeps this project useful: a request without a due date is not accepted. Sales work always has a date, usually a call with the customer, and the ticket should carry it.
The recurring sales work nobody creates a ticket for #
Deals get attention because they are new. The routine does not, because it is the same every cycle, and it is the part that slips in the busiest week of the quarter. A typical sales calendar:
| Routine | Cadence | What goes wrong without a ticket |
|---|---|---|
| Pipeline review prep | Every Monday | Stale stages and close dates walk into the meeting |
| Forecast submission | Every Thursday, or the last working day of the month | Submitted late, numbers from memory |
| CRM hygiene sweep | Every two weeks | Duplicate accounts and dead deals pile up |
| Renewal check, 90 days out | Monthly | A renewal is noticed a week before it lapses |
| Quarterly business reviews with key accounts | Every quarter | Booked late, prepared the night before |
| Commission and quota reconciliation | First working day of the month | Disputes surface after payroll |
| Win/loss review | Monthly | Never happens, so nothing is learned |
Every row is a recurring ticket, and treating it as one gives it an owner, a due date and a place on the same board as the deal work. The renewal check is the one with real money attached: a monthly ticket that runs a saved filter for contracts ending in the next 90 days costs nothing to create and catches the renewal that was about to be missed.
How to create recurring sales tickets in Jira #
There are three ways, and the right one depends on how many routines you have and who maintains 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 |
| "Last working day of the month" | Whoever remembers | Needs a cron expression | Chosen in the form |
| A rep on leave | The ticket is not created | Created on time | Created on time |
| Cost | Time | Counts toward your plan's automation usage | App licence |
Clone by hand #
Keep a master ticket per routine and clone it each cycle. For one weekly pipeline review owned by a sales manager who never misses it, that is enough. It fails at quarter end, which is exactly when the forecast and the renewal check matter most.
A Jira Automation scheduled rule #
Jira Automation's Scheduled trigger can create a work item on a timer. A weekly pipeline review is simple. Monthly and quarterly routines need a cron expression, and our Jira cron expression guide covers the syntax and what it cannot say. Each run counts toward your plan's automation usage, explained in Jira Automation pricing. If the team already runs a few Automation rules comfortably, this is the natural next step.
A scheduling app #
Recurring Work Items for Jira is our app, and recurring tickets are the whole job. A sales routine becomes a rule in the project:
- Turn the app on for the sales project and choose who may schedule.
- Set the working week and add public holidays. A rule can then roll forward or back to a working day, or skip the occurrence, when its date lands on a day off. That is what "last working day of the month" needs.
- Create a rule per 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.
- Name each ticket with tokens, for example
Forecast {{now.date}}, so this week's ticket is not confused with last week's. - Put the checklist in the description and set the assignee, labels and a due date relative to 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 project it lives in, so the sales team's schedules never create tickets in anyone else's project. It is free for up to 10 users.
A starter set of recurring sales rules #
A set most sales teams can adopt on day one:
- Pipeline review prep, every Monday, due the same day. Description: update stage and close date on every deal you own, flag anything slipping, add next steps.
- Forecast submission, every Thursday, assigned to each rep or to the manager who rolls it up.
- Month-end forecast lock, on the last Friday of the month, or the last working day with holidays set.
- Renewal check, on the first Monday of the month. Description: run the saved filter for contracts ending in the next 90 days, open a deal support ticket for any that need pricing or legal.
- CRM hygiene, every second Wednesday: merge duplicates, close deals with no activity in 60 days, fill missing close dates.
- Win/loss review, monthly on the second Tuesday, with headings for Won and why, Lost and why, What to change.
- QBR booking, every three months on the 1st, one ticket per key account or one with a checklist of accounts.
If a routine has steps owned by different people, such as a QBR that needs a usage report from support and a roadmap slide from product, put those in subtasks. See Jira subtask template for ways to get the same subtasks every time.
Reporting on sales work in Jira #
With requests and routine on the board, a few saved filters answer the questions that usually take a meeting. Replace SALES with your project key:
- What is due this week?
project = SALES AND due <= endOfWeek() AND statusCategory != Done - Which requests are waiting on another team?
project = SALES AND status = "Waiting" AND updated <= -3d - What did the routine produce last month?
project = SALES AND labels = routine AND created >= startOfMonth(-1) AND created < startOfMonth()
Save each as a filter and add a subscription so the list arrives by email before the pipeline meeting. The Jira weekly report guide covers building the email.
When the manual way is enough #
Not every sales team needs a schedule. If you have one manager running one weekly review and a CRM that already reminds reps about renewals, a calendar invite is enough. Jira Automation is the right next step for a team that already uses it and has two or three routines. A scheduling app earns its place when the routine list passes what anyone wants to keep as cron expressions, when month-end dates keep landing on weekends, or when quarter end is the week the routine always slips.
If your whole company is in Jira and you are wondering how other teams set it up, our guides on Jira for marketing and Jira for finance use the same pattern for their own calendars.
Frequently asked questions #
Can Jira be used as a CRM? For a small team with a short pipeline, yes: Atlassian's lead tracking template gives you a board of opportunities from contacted to won or lost. It has no email logging or contact history, so most teams move deals to a CRM as they grow.
What should a sales team track in Jira if it has a CRM? The work around the deal: requests to engineering, legal and finance, approvals, and the recurring internal routine such as forecast and pipeline review prep.
Can Jira create the weekly forecast 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.