Scheduling an issue

On this page

You can schedule issue due dates in Jira Core to track, review, and inform teams about issues dates. This powerful scheduling feature lets you perform fixed and relative date searches based on specific due dates, as well as arbitrary search periods. You can also perform advanced searches using Jira Query Language. 

Scheduling an issue

To schedule an issue, populate its Due date field. You can do this either when creating an issue, or by editing the issue later.

To enable Issue Scheduling, at least one group or project role must be given the Schedule Issues permission by your Jira administrator. Only users with the Schedule Issues permission can populate the Due date field.

Searching by due date

You can use either basic search or advanced search to search for issues by their due date.

Using simple search

You can search for issues using the search form in Issue Navigator (see Searching for issues). There are two ways to search for issues based on the Due date field. The first way is using fixed date values, the second is using periods that are relative to the current date.

Fixed date searches

There are two text fields in the search form that allow searching based on the Due date field.

  • To search for all issues that are due after a certain date, enter the date in the Due After text field. For example, to find all issues that are due after 1st June 2010, enter 1-6-2010 in the Due After field. You can also click the calendar icon and use the calendar popup to select a date.
  • To search for issues that are due before a certain date, enter the date in the Due Before text field. For example, to find all issues that are due before 1st July 2010, enter 1-7-2010 in the Due Before field.

To search for issues that are due between two dates, enter dates in both the Due After and Due Before fields.

Relative period search

It's possible to perform a search that's relative to the time when it's run. For example, it's possible to search for issues that are due seven days from now. To do this, enter 7d in the Due Date To text field of the Issue Navigator. Any time this search is run, it'll find issues that are due within seven days.

The values that are entered in the Due Date From and Due Date To fields have to conform to a special syntax (described below). If you like, though, you can use the Due Date popup by clicking the icon to the right of the Due Date To text field to specify the search period.

Due Date Popup

Use the Due Date popup to search for issues that are:

  • Overdue at the time of the search – Choose Now overdue and click Update.
  • Overdue by more than a certain number of days – Choose More than, enter the number of days, choose "days", and click Update.
  • Due within a certain number of days, but aren't overdue at the time of the search – Choose Due in next, enter the number of days, choose and not from the overdue box, then click Update.
  • Due within a certain number of days, or are overdue – Choose Due in next, enter the number of days, choose or is from the overdue box, then click Update.
  • Due between two dates – Choose Between and enter a beginning and end date. A blank field means you're not constraining either the from or to date.

The In range option in the popup uses the relative period syntax described below.

Relative Period Search Syntax

The Due Date From and Due Date To fields use a special syntax to denote time period bounds. The syntax uses numbers followed by abbreviations for the time period. The abbreviations are "w" for weeks, "d" for days, "h" for hours, and "m" for minutes. For example, to specify 10 days in the future, use "10d" or "1w and 3d". To specify a period bound in the past, "-" sign before the time period. For example, to specify 2 days, 4 hours, and 3 minutes ago, use "-2d 4h 3m".

Using advanced search

You can use Jira Query Language (JQL) to search for issues by due date. See Advanced searching, and particularly the documentation on the due date field.

Last modified on Sep 12, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.