Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Search for issues, navigate to your work, use advanced search, and work with your search results.
Plan and view work across multiple teams, projects, and releases using Plans.
If you’re working in a company-managed project, here’s some common errors that you might encounter on your timeline:
Board filter exceeds issue limits
The timeline view of Jira Software can only show 5,000 issues at once with no more than 500 being at the parent level.
The timeline automatically excludes issues if they were:
moved to the Done status category more than a year ago
moved to the Done status category, and it has a due date from more than a year ago
To only display issues created within the last year:
From your project, select Issues and filters > Advanced search.
In the search bar, enter this query, but replace:
NAME with the name of your project
DATE with the dates you’d like to focus on
Your timeline contains corrupt issues
An issue is considered corrupt if certain details, like the issue type, status, status category, or rank settings are invalid. The details might have been missing when the issue was created or something might have gone wrong with a bulk import.
The timeline won’t display until the details in the corrupt issue are fixed.
To fix a corrupt issue, you must raise a support ticket. Our team will help fix the issue so you can continue using your timeline.
No parent issue type in project
In order for a timeline to show, your project needs to have an issue configured as an epic issue type. If this issue type has been deleted from your project, the timeline won’t show.
To check whether your project has an epic issue type configured:
Select > Issues, then select Issue types from the left menu.
In the Type column in the middle of the page, look for issues that are labeled as Epic.
If you don’t find one, you’ll need to configure an epic-type issue. Learn how to edit and create issue types in Jira Software.
Alternatively, parent issues could be excluded from your JQL query. To resolve this, your board admin needs to edit the filter query in the Board settings to include parent issues.
Parent issues don’t display on the timeline (Kanban)
The timeline is based on the same JQL filters as your board. If you’re using a Kanban board, it’s likely that your board will have a JQL filter that prevents parent issues from displaying on the board. The query could look like this:
project = FOO and issueType != Epic ORDER BY Rank
To display them on your timeline, an admin can remove the JQL query from the board filter, and add it to the Kanban board sub-filter instead.
To adjust your JQL filter:
If you’re not already there, navigate to your company-managed project.
Go to More (···) > Board settings.
In the General tab of your board settings, find Filter > Saved filter.
Select Edit filter query.
From your Filters settings, remove issueType != Epic. Run the search, then save your changes.
Return to the General tab of your board settings. Find Filter > Kanban board sub-filter.
Edit the query by hovering over the text. Paste and issueType != Epic clause into the field.
Select Update to save your changes.
My sprints aren’t showing on my Timeline
In order for a sprint to show along the top of your Timeline, it must be from the same backlog or board container as the Timeline. Sprints from other boards won’t show up.
The sprints also need to have dates set (such as closed sprints, active sprints, or a scheduled future sprint) that fall within the previous one year or the next two years. Anything outside this date range won’t be shown.
Accidentally converted a child issue type to a parent issue type
If you've mistakenly converted a standard issue type to a parent issue type, restore them to their original state with the following steps:
Delete the 'wrong' epic type (the one that was converted).
As part of the issue type deletion process, you'll be asked to which new issue type you'd like to move all your issues.
Select the new issue type you created.
Rename this new issue type to your old one, if you want to.
Recently completed issues not showing on your timeline
If Due date is hidden from your issues, recently completed issues might not be on your timeline. The first step is to confirm that your issues have the Due date fields enabled:
You must be an admin to use Find your field on the issue view.
To find a field on the issue view:
Open an issue.
Select ··· > Find your field.
Search for the field you want to find.
Select the field.
If the field is hidden, Jira generates a warning.
To surface non-default fields in your issues:
Navigate to Settings -> Issues
Select Field Configurations from the column on the left, then select Configure.
Search for the field you want to add in the search box or find it in the list, then select Show. If it’s already visible in your site, this button will say Hide instead.
Finally, select Screens on the line of the field you want to add to your issues, then select the projects to which you’d like to add this field.
When you’re done, scroll to the bottom and select Update.
I can’t see my project timeline. Instead, it says “Timelines are designed for a single project”
Commonly, teams running a company-managed project create boards with a custom JQL query to monitor issues from multiple projects. However, the timeline view in Jira Software only works with issues from the backlog associated with one project. If you’re using a custom JQL filter that draws in issues from multiple boards, adjust it to only include issues from one project. Learn how to adjust your JQL filter.
Cross-project planning is only possible in your plan, which is included with Jira Software Premium and Enterprise. Learn more about how Advanced Roadmaps helps you plan across multiple teams.
Was this helpful?