What is the architecture of the Forge Jira application, given that it's a Function as a Service (FaaS) application? I'm curious about how the application logic is structured and how the various components interact with each other. Is it based on a serverless computing model, and if so, what are some of the key characteristics of this architecture? I'm asking this question to better understand how the Forge Jira application is designed and to gain insights into how FaaS architecture can be used in enterprise software development.
Hello,
Do you want to write a listener or a mail handler? If you write a listener, then you should attach this listener to the Create Issue Event and put all your logic in this listener. But you will not be able to distinguish, if an issue is created by mail or somehow else.
Could be mail handler but I'm stuck with this tutorial (creating a custom mail handler) and don't know how to force this to catch all issue not only what will put intro configuration
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.