Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-19750

Force new tickets for specified Issue Sources to go automatically into the Later release

    XMLWordPrintable

Details

    • 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 Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.

      Right now tickets are all going into whatever the next release is in order. For some projects that makes sense. For some it doesn't. Is there a way to tell Portfolio when its Calculating the release to use to default to Later instead of looking at the list of releases? I'm getting Releases with dates that are shifting, not because of the already scheduled items, but because of new items that should never have been assigned to that release.

       

      See mockup.

      Attachments

        Issue Links

          is related to

          Suggestion - JPOSERVER-1730 Force new tickets for specified Issue Sources to go automatically into the Later release

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              1af05c5174a4 Nic Stransky
              Votes:
              26 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: