Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-2735

Propogate actions/transitions to linked issues


    • 4
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update - 19 March 2015

      Thanks everyone for your feedback. After consideration, we are closing this issue because we do not expect to address it in the foreseeable future. As is clear from the examples below, the ideal propagated action depends on the type of issue link and varies depending on your use case. Considering issue links can be arbitrarily defined, this would require adding logic in JIRA to handle certain types of links differently from others. Alternatively, we would need to add settings to configure propagated actions based on the issue links.

      Our belief is that the value doees not justify the expected increase in UI complexity or maintenance burden.

      As always, please don't hesitate to contact me if you have any questions.

      Dave Meyer
      Product Manager, JIRA Platform

      When an issue is linked as solved by or set as duplicate do a cascading update when resolving the issue that solves the duplicate.

            Unassigned Unassigned
            6b3d82bb8469 Vincent van Wichen
            72 Vote for this issue
            55 Start watching this issue