Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-3230

Due dates on "versions", and auto updates of "issue" due dates

    XMLWordPrintable

Details

    • 0
    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      It would be nice if "versions" had due dates (for example 7.2 alpha is due on 1/3/04), and if all the "issues" (say bugs) for that version could inherit it's due date or something.

      Perhaps when changing the due date on the version, it could prompt for which related issues to update. This would mean that you wouldn't have to go and change say 30 issues' due dates manually (UGH!)

      Attachments

        Issue Links

          has a derivative of

          Suggestion - JRACLOUD-27119 If issue's due date unspecified, inherit the due date of the fix version

          • Closed
          is related to

          Suggestion - JRACLOUD-9847 Assign due date of issue the same as fix version of release date.

          • Closed

          Suggestion - JRACLOUD-61101 Version Release/Unrelease will update in Issue Ticket

          • Gathering Interest

          Suggestion - JRASERVER-3230 Due dates on "versions", and auto updates of "issue" due dates

          • Gathering Interest
          relates to

          Suggestion - JRACLOUD-5745 Due date of parent task = last due date of subtasks

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              f800ce91ec82 Craig O'Shannessy
              Votes:
              23 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: