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

Link and workflow transition improovement

    XMLWordPrintable

Details

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

    Description

      Here some customization requests related to Link Features.

      We have define that ISSUE-1556 block ISSUE-1555 that block ISSUE-1557.

      1. Automatically "Waiting for" for ISSUE-1557
      When we define that ISSUE-1557 is blocked by ISSUE-1555 (or ISSUE-1555 block ISSUE-1557), ISSUE-1557 should be put automatically as "Waiting For"

      2. Automatically "ReOpen" for ISSUE-1557
      When all the blocking issue linked to ISSUE-1557 are in Resolved/Fixed, then -1557 is automatically put as "Reopened"

      3. Condition the transition to Resolved for ISSUE-1557.
      Alive 1557 should be able to pass in Resolved status only if ISSUE-1555 and ISSUE-1556 are resolved themselves firstly.
      If ISSUE-1555 and ISSUE-1557 are not resolved, ISSUE-1557 cannot be put as Resolved

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              12096eed3ab2 Ubisoft
              Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: