How to Add a Start Date to a Jira Epic

If you’ve ever stared at a Jira epic and wondered why there’s no start date field staring back at you — you’re not alone. Thousands of teams hit this wall every week. The fix is simpler than you think, but the path to it isn’t obvious.

This guide walks you through every method, every workaround, and every setting you need to get start dates working on your epics today.

Why Jira Epics Don’t Show a Start Date by Default

Jira doesn’t always surface the start date field by default — especially in Jira Cloud. The field exists, but it’s either hidden in your board settings, not mapped to your screen, or disabled in your project configuration.

According to Atlassian’s own community data, start/end date configuration issues are among the top 5 most-asked questions in Jira support threads. You’re not missing something obvious. The product design simply buries this feature.

Here’s what’s actually going on under the hood:

• In Jira Cloud, epics have a “Start date” and “Due date” field natively — but they may not appear in your create/edit screens
• In Jira Server/Data Center, the same fields exist but require manual field configuration or a plugin in older versions
• In team-managed projects, the field behavior differs from company-managed projects

Knowing which project type you’re working in is step one.

How to Check Your Jira Project Type

Before you change anything, confirm whether you’re in a team-managed or company-managed project.

Go to your project → click Project settings in the left sidebar → look at the bottom of the sidebar for the label. It will say either “Team-managed project” or “Company-managed project.”

This matters because the fix is different for each.

Adding a Start Date to a Jira Epic in a Company-Managed Project

Company-managed projects give you full admin control over field configurations. Here’s how to enable the start date field:

Step 1: Go to Project Settings

Navigate to your project → click Project settings → then Issue types from the left menu.

Step 2: Select the Epic Issue Type

Click on Epic from the list of issue types. This opens the field editor for epics.

Step 3: Add the Start Date Field

On the right side, you’ll see a panel labeled “Drag a field type to one of the sections on the left.” Scroll through that list and look for Start date. Drag it into your field layout — either in the “Description” section or the “Date” area.

Step 4: Save Your Changes

Click Save changes at the top right.

Now when you open or create an epic, the start date field will appear in the issue detail view.

Pro tip: If you don’t see “Start date” in the available fields panel, it may be named differently depending on your Jira version. Look for “Epic Start Date” or check if a custom date field is being used instead.

Adding a Start Date to a Jira Epic in a Team-Managed Project

Team-managed projects use a simplified field editor. The process is slightly different.

Step 1: Open Any Epic

Click into an existing epic in your project.

Step 2: Look for the Date Fields

Scroll down in the issue detail panel. Jira team-managed projects often show a “Start date” field already — it may just be empty and visually subtle.

Step 3: Click the Start Date Field

Click on it and a date picker will appear. Select your start date and it saves automatically.

If you don’t see the field at all:

Step 4: Add It Through Project Settings

Go to Project settings → Issue types → click Epic → then use the field panel on the right to drag Start date into the layout.

How to Set Start Dates on Epics Using the Roadmap/Timeline View

If your team uses the Roadmap or Timeline view (available in Jira Software), you can set start dates directly from there — no settings menu required.

Step 1: Open the Timeline View

In your project, click Timeline (or Roadmap) from the left sidebar.

Step 2: Find Your Epic

Epics appear as colored bars across the timeline. If a bar has no start date, it will appear as a dot or a very short stub on the left.

Step 3: Drag to Set the Date

Hover over the left edge of the epic bar. Your cursor will change to a resize arrow. Click and drag it left or right to set the start date visually.

Step 4: Confirm the Date

Click on the epic to open its detail panel. Verify the start date field now shows the date you just set.

This method is faster for teams that work visually and manage multiple epics at once. According to Atlassian, teams using roadmap views report 30% faster sprint planning cycles compared to teams managing epics purely through list views.

Why Your Start Date Field Might Still Not Appear (And How to Fix It)

Even after following the steps above, some teams still don’t see the field. Here are the most common reasons and fixes:

The field is on a different screen

Jira uses “screens” to control which fields appear in Create, Edit, and View modes. The start date might be added to the field layout but not mapped to all three screens.

Fix: Go to Project settings → Screens → check that Start Date is included on the Edit Issue and View Issue screens, not just the Create screen.

You don’t have the right permissions

Only Jira admins can modify field configurations in company-managed projects. If you’re not seeing the settings options described above, you likely need to ask your Jira admin to make the change.

You’re using a custom field instead of the native one

Some teams create a custom date field called “Epic Start Date” or “Planned Start.” If your organization has done this, the native field may not be in use. Check with your admin to see which field is the official one.

The field is hidden by a filter

In the issue detail view, Jira sometimes collapses empty fields to reduce visual clutter. Look for a “Show more” or “+ X hidden fields” link at the bottom of the issue details panel and click it to reveal all fields.

How to Bulk Add Start Dates to Multiple Epics

If you have a backlog of epics all missing start dates, going one-by-one is painful. Here’s a faster approach.

Using the Backlog or Epic Panel

Go to your Backlog view. Click on an epic in the left panel. The detail view opens on the right. Set the start date there. Move to the next epic. This is faster than opening each epic individually.

Using Jira Bulk Edit

Jira’s bulk edit feature doesn’t natively support date fields in all configurations, but it works for some setups:

Go to Backlog → select multiple issues using the checkbox → click Actions → Bulk Change → Edit Issues → look for Start Date in the field list.

Using CSV Import

If you’re migrating a large batch of epics or updating dates from a spreadsheet:

Export your epics as CSV → add/update the Start Date column → re-import using Project settings → Import Issues (or use a Jira admin CSV import).

Research from the Project Management Institute shows that teams who consistently track start and end dates on initiatives complete projects 28% more on time than those who don’t track dates at all.

Adding Start Dates in Jira Server and Data Center

If you’re running Jira Server or Data Center (self-hosted), the process is similar but goes through the global administration panel rather than project-level settings.

Step 1: Go to Jira Administration

Click the gear icon in the top right → Issues → Field Configurations.

Step 2: Find Your Field Configuration Scheme

Locate the field configuration scheme used by your project. Click Configure next to it.

Step 3: Enable the Start Date Field

Find Start date or Epic Start Date in the field list. If it shows as “Hidden,” click Show to make it visible.

Step 4: Map It to Your Screen

Go to Administration → Issues → Screens. Find the screen used by your Epic issue type. Click Configure → Add Field → select Start date → save.

Step 5: Verify in Your Project

Open any epic in your project. The start date field should now appear in the edit view.

Note: In Jira Server versions prior to 8.x, the Epic Start Date may be stored differently. Some teams use plugins like BigPicture or Advanced Roadmaps (now built into Jira Software Premium) to get richer date management on epics.

Using Advanced Roadmaps for Start Date Planning

Teams on Jira Software Premium have access to Advanced Roadmaps, which gives you the most powerful start date management available in Jira.

With Advanced Roadmaps you can:

• Set start and end dates across multiple levels (epics, stories, sub-tasks)
• Use dependencies to auto-shift start dates when blockers change
• See team capacity alongside date ranges
• Schedule with sprints or dates depending on your preferred planning method

To access it: Go to your project → Plans in the left sidebar → create or open a plan → epics will display with editable start/end date fields directly in the view.

Advanced Roadmaps users report completing cross-team planning 40% faster than teams using manual spreadsheets for the same purpose, according to Atlassian’s internal benchmark data.

Best Practices for Managing Epic Start Dates

Getting the field visible is only half the job. Using it well is what actually improves your planning.

Set the start date before sprint planning, not after. Too many teams add start dates retrospectively. A date added after the fact is a record, not a plan. Set it during your backlog refinement session so the team commits to it.

Align start dates with dependencies. If Epic B can’t start until Epic A ships a critical feature, that dependency should be reflected in the start date. Jira’s dependency markers in Timeline view help teams visualize this.

Review start dates in weekly planning reviews. Studies show that projects with weekly schedule reviews are 2.5x more likely to finish on time than those reviewed monthly or ad hoc.

Use start dates alongside due dates, not instead of them. A start date without a due date is a wishlist. Both fields together create a commitment with accountability.

Don’t over-granularize. Epics are meant to represent weeks or months of work. Trying to pin them to exact days creates false precision. Use weeks as your unit of granularity for epic-level planning.

Conclusion

Adding a start date to a Jira epic isn’t complicated once you know where to look — but Jira’s layered settings make it easy to miss. The key is knowing your project type, accessing the right configuration screen, and making sure the field is mapped to the issue screens your team actually uses.

Once your start dates are in place, the real work begins: keeping them accurate, reviewing them regularly, and using them to drive real accountability across your team.

Teams that treat planning as a live system — not a one-time setup — consistently outperform those that don’t. The same discipline that makes your Jira epics predictable can be applied to your outbound pipeline. If your lead generation is as inconsistent as a Jira board without dates, SalesSo can fix that.