Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-6585

Has Review Condition

XMLWordPrintable

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

      I would like to have a condition that prevents a workflow if the Issue does not have any linked review.

      I know there is the "Unreviewed Code Condition" but this goes too far for us as there are some commits you don't want to have in your review, or are merge commits or are commits commited to this Issue by accident (wrong ticket number in commit message).

      All this led to much discomfort with using the above condition and therefore we disabled it.
      However the main reason we added this condition in the first place was because we always want an Issue to have at least one review.

      I tried to solve this by using the "Calculated Number Field" (from JIRA Misc Custom Fields plugin) but was not able to create a number field that returns the count of linked reviews (but I was btw. able to create a field that counts the number of sub tasks, so a Story can't be started without ones. Great plugin!)

      Or is there any other way I can accomplish this?

          Form Name

            [CRUC-6585] Has Review Condition

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3020779 ] New: JAC Suggestion Workflow 3 [ 3634273 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2946219 ] New: JAC Suggestion Workflow [ 3020779 ]
            Owen made changes -
            Resolution Original: Timed out [ 10 ]
            Status Original: Resolved [ 5 ] New: Not Being Considered [ 11776 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage [ 940309 ] New: Confluence Workflow - Public Facing v4 [ 2946219 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Owen made changes -
            Issue Type Original: New Feature [ 2 ] New: Suggestion [ 10000 ]
            Marek Parfianowicz made changes -
            Fix Version/s New: N/A [ 54415 ]
            Resolution New: Timed out [ 10 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

            Marek Parfianowicz added a comment -
            Atlassian Update – 5 October 2018

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Regards
            Marek Parfianowicz
            Fisheye/Crucible TL

            Marek Parfianowicz added a comment - Atlassian Update – 5 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Regards Marek Parfianowicz Fisheye/Crucible TL
            Marek Parfianowicz made changes -
            Labels Original: condition existing fusion jira-crucible-workflow-condition review New: condition existing fusion jac-cleanup-phase4 jira-crucible-workflow-condition review
            Piotr Swiecicki made changes -
            Labels Original: condition existing fusion review New: condition existing fusion jira-crucible-workflow-condition review
            Piotr Swiecicki made changes -
            Workflow Original: FECRU Development Workflow (Triage) [ 553723 ] New: FECRU Development Workflow - Triage [ 940309 ]

              Unassigned Unassigned
              a6e0a1e76b4a Gustav Rek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: