Jira hosting: Cloud, Server, Data Center
Due Date (1) field can be completed in 3 4 ways:
Fixed (2): here you can enter a specific
valuedate that you want to
enter in thebe a due date
field.
Dynamic (3): that way add a specified value to the current date. For example, if you set "1d" in the field, due date will be set on next day after the creation. Or in case "1w", it will be next week.
Next Execution Time (4): In this case the due date will be set to date when the scheduler will be run this Scheduled Job again.
End of the month Offset (5): (available only in Server, Data Center): due date will be set to the end of the month of issue creation. For example if you set “2d” in field, it means that due date will be set two days before the last day of the month. Leaving the field empty equals setting the due date to the last day of the month.
| Info |
|---|
Note: By default Due Date field is a date field type (not date time), that's why the smallest period is 1d (1 day). If you would like to have due date as creation date in Dynamic due date use 0d |
This field is located on the second screen (5) of creation/edition form (available to get here on the "Set Issue Details" screen). It is present by default in all Jira Business (not Software) default projects.
%20-%20Setting%20a%20Due%20Date%20Field%20via%20TSP%20-create_si_wizard_issue_details_pliki.png?version=1&modificationDate=1545040440359&cacheVersion=1&api=v2)
...
...
Sometimes you may not see "Due Date"
| Info |
|---|
This happens because all the fields on this screen (and other screens of TSP) are being taken from the Jira's fields, so if a particular field was disabled by Jira or Project admin, then you won't be able to see it here. Moreover sometimes there are fields generated entirely by other add-ons and they may also be invisible or working in a faulty/glitch way. To resolve such issues feel free to get in touch with us. |
...