-
Suggestion
-
Resolution: Duplicate
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
If an issue does not have a due date specified, it should use the due date of its fix version if the version has a due date.
This is implicit and only works for a blank due date field in the issue. If the issue's due date field has a value, that will always take precedence.
- derived from
-
JRASERVER-9847 Assign due date of issue the same as fix version of release date.
- Closed
-
JRASERVER-3230 Due dates on "versions", and auto updates of "issue" due dates
- Gathering Interest
- duplicates
-
JRASERVER-9847 Assign due date of issue the same as fix version of release date.
- Closed
- relates to
-
JRACLOUD-27119 If issue's due date unspecified, inherit the due date of the fix version
- Closed
- was cloned as
-
JRASERVER-30275 build index If issue's due date unspecified and inherit the due date of the fix version is done
- Closed
If issue's due date unspecified, inherit the due date of the fix version
-
Suggestion
-
Resolution: Duplicate
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
If an issue does not have a due date specified, it should use the due date of its fix version if the version has a due date.
This is implicit and only works for a blank due date field in the issue. If the issue's due date field has a value, that will always take precedence.
- derived from
-
JRASERVER-9847 Assign due date of issue the same as fix version of release date.
- Closed
-
JRASERVER-3230 Due dates on "versions", and auto updates of "issue" due dates
- Gathering Interest
- duplicates
-
JRASERVER-9847 Assign due date of issue the same as fix version of release date.
- Closed
- relates to
-
JRACLOUD-27119 If issue's due date unspecified, inherit the due date of the fix version
- Closed
- was cloned as
-
JRASERVER-30275 build index If issue's due date unspecified and inherit the due date of the fix version is done
- Closed