Comments
-
Hi! We have made the decision to roll this change back. We have been carefully monitoring feedback from our customers and we recognize that this change has negatively impacted customers who use this feature as an integral part of their workflow. We are glad to make this feature available again to help our customers use our…
-
@Bill Wesel your experience is definitely not the kind of experience we want our customers to go through. We have updated our internal process to avoid such a thing from happening again. While we have to sometimes make tough decisions about the functionality our product offers, the communication around such decisions needs…
-
Hi David! I'd love to help you achieve your goal but first please allow me to better understand some specifics about your cofiguration. First off, what type of pipelines do you run on your PRs? Please refer to this blogpost in case my question is confusing. I would like to know if you run `branches` or `pull-request`…
-
I will be closing this BCLOUD since an endpoint with this capability exists, so I thought I'd add the note here too. Specifically, the pullrequests endpoint (the second one provided above) supports querying, which supports "reviewers.uuid" as well as "author.uuid". To get a list of open PRs authored or reviewed by a user…
-
Hi! Above all I'd like to very sincerely apologize for the frustrations our product is clearly causing you and your team! We don't take this lightly. We are engineers ourselves and we know exactly how important good tooling is for what we do. Please believe me when I say we strive to resolve issues with our product so our…
-
I was facing the same problem. When two people collaborate on a single Jira ticket, we use a custom field to mark the second assignee. I wanted that one ticket to appear twice - in two swim lanes, each swim lane belonging to one team member, one as an assignee and one as a second assignee. But I couldn't do it, for the…
