Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-13425

JIRA Workflow condition in terms of non open/closed code review statuses

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • None
    • None
    • 1
    • 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

      Hi
      We all agree that a JIRA ticket would transition if its linked code reviews are reviewed and closed. If one of these code reviews is open, then the JIRA issue shouldn't be transitioned.
      However, there is an issue (in my opinion) for it: What happens when a linked code review is at Draft, Abandoned or Summarized state? What it seems is that there is a code change committed against the ticket and its Crucible code review is created but is on Draft state. At the JIRA ticket side, there are transitions that shouldn't appear because of the code review is not closed regardless of being reviewed or not.

      Is there a way that at JIRA workflow transition, set a condition that the ticket shouldn't be transitioned when at least one of the code reviews is open, draft, abandoned, or summarized.

      Thanks

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              c357ac0206f0 Darly Senecal-Baptiste
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: