Now if you are looking to create a field with java code embedded, then that's a NO. You maybe able to add some code using marketplace add-ons that extend custom field capabilities.
So basically we don't have the SDK functionality in cloud now where we can build our custom field if I understand that right from your 2nd statement. (Like how we had for server)
Also , do you have any reference to end to end guide of building API using java ? I understand the the link has only the src code.
Thank you once again.
Regards
Kaushik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unlike on-premise versions, where you could extend products with new capabilities using the Atlassian SDK, the equivalent for cloud is the Forge platform. It’s entirely possible to create your own custom fields on cloud, but you’ll be working with JavaScript rather than Java.
Forge runs on Atlassian’s infrastructure and handles most of the heavy lifting for you.
Thankyou @Sarp Egemen . Yes using Forge will be the way ahead, thanks.
However I wanted to know if the API calling has been supported using Java, definitely you can do lot of things using that , so what exactly is supported using Java i.e. if in the below link suggested by Benjamin, most of the things I can do using Java API (along with python, forge and so on...),
How would the ecosystem look like in this case i.e. to be very specific ,
If you see the forge tab of any API , its understod that the index.js file should contain this code, where I do have other dependencies as well like manifest.yml , src folder etc.
Similarly , if I have to use the Java capability of API, how should my other components look like in the IDE view ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
REST APIs (and GraphQL, for that matter) are language agnostic. You can call them from any language that supports HTTPS, including Java.
If you decide to go the Forge route, I highly recommend checking out the learning path I mentioned earlier, along with the official documentation.
To quickly recap, as you asked: manifest.yml is where you declare the components that will extend Jira (or any other Atlassian app), while index.js (which can be named differently if specified properly) is the entry point for the front end.
When building a Forge app, keep in mind that the platform is opinionated: there’s no straightforward way to set up an ecosystem with a hosted Java backend and connect to it from the front end. That approach belonged to the previous platform (Connect, which is now sunset).
Now, with Forge, backend functions (called resolvers) run in a FaaS environment, fully managed by Atlassian and written in JavaScript (or TypeScript, of course).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.