Edmund Munday Atlassian Team

Hi @Aurimas Navardauskas & @Sebastian Hesse - we've just released an update for the Pipelines API's that make the following sets of API's callable from Forge apps (both Custom Merge Checks & Dynamic Pipelines). -…

Thanks @Alex Figliolia Issues with labels: Thanks for the extra details, this is exactly what we needed to validate our thinking. The current plan is for the limit to be 10KB once fully parsed to JSON. Custom Deployment Variables: Just for my context (sorry if I’m missing something!), does the changes we made to give you a…

Hi @Yannis Argyropoulos [_ScriptRunner - The Adaptavist Group_] & @Aron Gombas _Midori_ - a few points on this: * There are currently 3 triggers:* `on-code-pushed` * `on-reviewer-status-changed` * `on-merge` * Today, you would use an `on-merge` trigger for most of the use-cases you cited there.* This is basically your…

Hey @Alex Figliolia - * Deployments/Environments: Thanks for the extra info, we'll have a think about ways it would make sense to incorporate it. Just to set expectations, the initial support for these endpoints in Forge will be the same API's as are available today as that allows us to move quickly.* Other API's we've got…

Hi @Aurimas Navardauskas - this is something we're working on adding right now. We expect to have this available in the next few weeks. We'll post an update here when they are shipped.

Hi @Juan Carlos - awesome question, thanks for asking! * This is 100% possible today, and very simple. * The first step is to use the `requestBitbucket` Forge API function to call the Bitbucket API to retrieve all the commits on the Pull Request.* The API for that is documented…

Hi @Alex Figliolia - thanks so much for sharing this detailed feedback! It means more to us than you might think having the community so engaged with these new capabilities, and we're excited that you're seeing this stuff as valuable. * JS-Doc/Typescript: Stay tuned! We're hoping to get `d.ts` files available for all the…

Hey @Michael Rüegg _Mibex Software_ - another excellent question! There's a bunch of important information to share regarding rate limits, so I'll put it all here. * Firstly, the way API rate limits are calculated for Forge apps is totally different to Connect apps.* Each Forge app is an entirely seperate "identity" and…

Hi @Arend Lapere - Thanks for the awesome feedback, so glad you found it easy to setup and start using, that's been a huge focus for us. Today, Project / Workspace Checks are not available sorry! That's next on the list though, so stay tuned. I'd love to learn a bit more about your use-cases for Project level vs Workspace…

Hi @Michael Rüegg _Mibex Software_ As of today, it's unfortunately not something we're investing heavily in for Bitbucket cloud, for two primary reasons. * Bitbucket Cloud's traditional Connect implementation is not 100% standardised with the wider Atlassian Connect ecosystem (unlike our Forge implementation, which is 100%…

@Alex Figliolia - just a quick note to say that these endpoints are coming very soon, the team is just wrapping up work on a major Forge related release for Pipelines, and then we'll be moving over to supporting all the remaining Pipelines related API's in Forge.

Hi @Gergely Juhász _Midori_ Public - really excellent question, thanks for asking! The short answer is "This is a limitation of the open beta", when we go to GA, the behaviour between the two types of Checks will be effectively harmonised, at least in terms of standard/premium - however Custom Merge Checks will have a…

@David - apologies for the slow reply! More than happy to chat, feel free to put 30 mins in my calendar via: https://calendar.app.google/hdvBYutokvN7uHem7 I'm based in AU, so depending on where you are, the times on there might or might-not work for you.

@Garrett_LoVerde - this is a really excellent point and you are 100% correct. Something the team is working on right now is library of helper functions that is published as an NPM module that can be included in any Forge Apps being built. These helper functions are designed to abstract away the complexity of common tasks…

Hi @shani.feldboy - just checking in, how did you go with this, were you able to get up and running?

Hi @Aron Gombas _Midori_ First up, thank you for raising these issues, we do genuinely appreciate it and it makes a significant difference to the direction of this work. Additionally, I want to apologise for the time it’s taken to get an official response back to you. To reiterate the issue: * Whilst Custom merge checks do…

@NC - only 6 months late... sorry! What are your thoughts on using JSM to receive new JPD requests and then using automation to clone into JPD and keep the two issues coordinated? We currently have this logic implemented for Incidents and linked Bugs within Jira software but if there was some sort of JPD portal in the…

Hi @Leon Meier - sorry I missed the earlier notification for this. Are you able to share a screenshot of the full "update field" JSON you're inputting? @acorvino - It looks like the issue you might be having is just down to the syntax of the JSON you're using for the update. Rather than specifying "update", you should just…

Hi @Eduar Bastidas - looking at that Github thread, it appears that Composer issue is being caused by changes made in Compose 2.7.0 and was resolved when the user pinned Composer to 2.6.6. https://github.com/pestphp/pest/issues/94#issuecomment-1936233204

Hi @Aron Gombas _Midori_ - apologies for the slow reply, I didn't see the initial notification for your comment for some reason. I'll review this with the team today to understand the behaviour you're experiencing.

Hi @Jan Ulrich Robens - apologies about this. It should be something along the lines of: const App = () => { const repoUUID = < some repo ID >; // get the string stored in Forge Storage. const storedString = await storage.get(repoUUID); return ( <Text > {storedString} </Text> ); } The `useEffect` hook you had in your…

Hi @antoine.doeraene - thanks for the question! For context, I'm the Product Manager who looks after the teams leading our Forge project. Your use-case is something I'd love to discuss with you in more detail would you be available for a 30 minute Zoom call at some point? If so, my calendar booking link is here, please…

Thanks @Michael Rüegg _Mibex Software_ - two parts to this answer. 1. In terms of a more public way of communicating what's coming, this is a great idea. I'll see what the best tool for this is right now, might be a good use-case for a Jira Product Discovery view (Subtle plug). 2. In terms of Project level: yes, we 100%…

Hi @Steffen Opel _Utoolity_ - thanks for this. It's an excellent question, we already have something equivalent to this in Bitbucket Cloud (Workspace Settings => Marketplace) for legacy Connect Apps. We don't currently have any plans for an in-product Marketplace for Forge apps, solely because we're focussing on pushing…

Hi @Aron Gombas _Midori_ - thanks for this question, I genuinely do appreciate it as every one of these we get helps me build the case for PvA BBC Apps. I can't give you a specific timeline, but what I can say is that this is something I've been actively building a case for over the last several months, and the momentum…

Hi @Aron Gombas _Midori_ - Right now, we don't have Checks for rejecting Push's as something we could give you a date for. Our initial focus is on Checks for PR's as that's something we can deliver significantly faster and solves a wider range of use-cases. We will look at Forge Checks on code-push at a later date, but it…

Hi @Aron Gombas _Midori_ Sorry I took ages to get back to you. We've recently gone live with our open EAP of Forge in Bitbucket Cloud, which is what all these capabilities will be based on. Can I ask a favour of you? Head over to the new Community Group for Forge Beta and request to join. Once you're in, can you please…

Hi @Aron Gombas Thanks for the questions, the initial release of Custom Merge Checks will primarily be targeted at customers wanting to use Forge to write their own custom logic into their PR process using Forge. We are planning to bring Bitbucket Cloud Forge apps to the Atlassian Marketplace, and are working through a…

Hi @Omer Meshar - in response to your question, for our internal processes we setup the JPD permissions fairly openly, so members of the internal team who create idea (engineers etc) also have permissions to edit the fields on those ideas too. This way they can easily make the changes they need in terms of escalations etc.…

Sorry for the confusion @Francisco Aguiar Project-level Branch Permissions and Merge Checks will start rolling out in the coming weeks. Project-level Pipelines Variables are not something we expect to be able to work on until later in 2023.