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

Restrict workflow based on status of linked issues (dependencies)

XMLWordPrintable

    • 5

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

      Atlassian Update – 13 Jan 2016

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days, including the attachment "screenshot-1.jpg"; however there are no immediate plans to put this suggestion on our near term roadmap.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Daniel Franz
      dfranz@atlassian.com
      Principal Product Manager, JIRA Platform

      Whilst experimenting with the issue linking functionality, we came up with the idea that as well as just linking, it would be great if we could add a dependancy on another issue. So we can setup a work-flow that says "before IS-334 can be done, IS-331 and IS-332 must be compleated."

        1. 54566406.jpg
          54566406.jpg
          89 kB
        2. screenshot-1.jpg
          screenshot-1.jpg
          9 kB

              Unassigned Unassigned
              e4f74cf81faf Mark Derricutt
              Votes:
              126 Vote for this issue
              Watchers:
              75 Start watching this issue

                Created:
                Updated:
                Resolved: