nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Explain all the various "Date" fields in JIRA

Andrew Blake_igx0ua

I'm working on a project that requires filtering issues by date, but JIRA has so many possible date fields (Created, Sprint Start Date, and Change Date, just to name a few) that it's really hard to know what is what. Here is a list of the date fields that are still frustratingly unfamiliar. Can somebody please explain what each of them mean so that I know which one to use?

Actual Start/End date

Baseline start/end date

Change completion date

Change start/end date

Date Change

Effective Date

Start Date/End Date

Issue Date

Satisfaction Date

Scan Date

Term Date

Updated

———————————————————

Thank you so much!

Accepted answers

Steven F Behnke

Actual Start/End date <- Custom Field, ask your Jira admin
Baseline start/end date <- Custom Field, ask your Jira admin
Change completion date <- Custom Field, ask your Jira admin
Change start/end date <- Custom Field, ask your Jira admin
Date Change <- Custom Field, ask your Jira admin
Effective Date <- Custom Field, ask your Jira admin
Start Date/End Date <- Custom Field, ask your Jira admin
Issue Date <- Custom Field, ask your Jira admin
Satisfaction Date <- Custom Field, ask your Jira admin
Scan Date <- Custom Field, ask your Jira admin
Term Date <- Custom Field, ask your Jira admin
Updated <- Last time any field was updated on the issue

All comments

Steven F Behnke

Actual Start/End date <- Custom Field, ask your Jira admin
Baseline start/end date <- Custom Field, ask your Jira admin
Change completion date <- Custom Field, ask your Jira admin
Change start/end date <- Custom Field, ask your Jira admin
Date Change <- Custom Field, ask your Jira admin
Effective Date <- Custom Field, ask your Jira admin
Start Date/End Date <- Custom Field, ask your Jira admin
Issue Date <- Custom Field, ask your Jira admin
Satisfaction Date <- Custom Field, ask your Jira admin
Scan Date <- Custom Field, ask your Jira admin
Term Date <- Custom Field, ask your Jira admin
Updated <- Last time any field was updated on the issue

Nic Brough -Adaptavist-

Good answer - concise and accurate. I wanted to add the example fields in the main question too:

Created <- date the issue was added to Jira
Sprint Start Date <- date the sprint was, or will be, started
Change Date <- Custom Field, ask your Jira admin

Steven F Behnke

Thanks nic

Andrew Blake_igx0ua

Thanks both! I didn't realize these were mostly custom fields. I'll check with my admin.

unknown

I know this is an old thread, so I'm hoping something has changed.

Is it possible to have the sprint start and end date columns in the structure automatically calculated based on when the 'Start Sprint' button was clicked plus the default sprint duration?

If I have 10 stories in a new sprint, I don't want to have to update each story individually or update the dates if the story changes sprints.

M B_fk2ouy

Using Jira Automation, you can automate the calculation for every Story/Tasks in a new Sprint when it starts.

_string_

Additionally, If you have, BigPicture by Softwareplant, it will create and/or leverage both the "Start date" and "End date" custom fields:

https://wiki.softwareplant.com/pages/viewpage.action?pageId=228426612

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server