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

As a JIRA Portfolio user, I want to set dependencies between version releases.

    XMLWordPrintable

Details

    • 4

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

      While dependencies can be set between story/story, story/epic, epic/story and epic/epic, I want to also be able to set dependencies between version releases.

      For example, Adapter v2.0 depends on full completion of Platform v5.2. Adapter v2.0 and Platform v5.2 would be on separate release streams. Effort (stories/tasks) are not always associated with epics.

      Attachments

        Issue Links

          is related to

          Suggestion - JSWCLOUD-21017 As a Product Manager forecasting feature development, I want to link issues to Releases as dependencies.

          • Closed

          Suggestion - JPOSERVER-362 As a JIRA Portfolio user, I want to set dependencies between version releases.

          • Gathering Interest
          mentioned in

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              0a610f8c2094 David Maurizi
              Votes:
              61 Vote for this issue
              Watchers:
              22 Start watching this issue

              Dates

                Created:
                Updated: