Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-1730

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

XMLWordPrintable

    • 0

    • JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      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.

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

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

            Nic Stransky added a comment -

            Not sure how this isn't getting any response from the JPO team. Doesn't seem like a destructive change, and clearly a lot of people are wishing to have this level of control over more complex portfolio plans with multiple products and fixversions to manage.

            Nic Stransky added a comment - Not sure how this isn't getting any response from the JPO team. Doesn't seem like a destructive change, and clearly a lot of people are wishing to have this level of control over more complex portfolio plans with multiple products and fixversions to manage.

            Liandro Rossini added a comment - - edited

            Nice idea, but (in our scenario) we still would have to set the "release" for the earlier items. 

            We use kanban + continuous delivery.. so we don't have to set any release.

            Considering this, the solution for the "minor manual effort" would be an option for we just to set and portfolio "do not antecipate any story".  No release setting needed. 

            Liandro Rossini added a comment - - edited Nice idea, but (in our scenario) we still would have to set the "release" for the earlier items.  We use kanban + continuous delivery.. so we don't have to set any release. Considering this, the solution for the "minor manual effort" would be an option for we just to set and portfolio "do not antecipate any story".  No release setting needed. 

              Unassigned Unassigned
              1af05c5174a4 Nic Stransky
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Archived: