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

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • 0

      NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? 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.

            Assignee:
            Unassigned
            Reporter:
            Nic Stransky
            Archiver:
            Aakrity Tibrewal

              Created:
              Updated:
              Archived: