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

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Plans - Timeline
    • None
    • 1

    • 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.

      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.

        1. these should be Later not some random release.png
          these should be Later not some random release.png
          79 kB
        2. portfolio issue sources force into later option.png
          portfolio issue sources force into later option.png
          58 kB

            [JRACLOUD-88043] Force new tickets for specified Issue Sources to go automatically into the Later release

            Eli Mata added a comment -

            Any news on this?  It seems like this is a basic use case.

            Eli Mata added a comment - Any news on this?  It seems like this is a basic use case.

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

                Created:
                Updated: