What does jira run on

If you were looking to integrate Jira with a Single Sign-On SSO solution, you would do so by writing a custom Seraph authenticator and in fact, many customers have done so. Please note that by default Jira is not shipped with any SSO integration, customers have to write a custom Authenticator themselves.

You may also want to check out Crowd and integrating Jira with Crowd. Another very important function that Seraph performs in Jira is to only allow users with Global Admin permission to access WebWork actions that allow the user to perform administration tasks. For more information on Jira's permissions, see Jira's documentation. For more information on how seraph works internally please see this page. Both Jira and Confluence now embed a subset of Crowd's core modules for powerful and consistent user management.

As mentioned previously, Seraph delegates to Embedded Crowd to authenticate the user i. Jira supports the use of Jira:PropertySet to store user preferences In Jira the preferences include things like:. In addition, Embedded Crowd also has its own concept of "User Attributes". The two concepts, although related, do provide different advantages and disadvantages, so plugin developers should consider their individual requirements in order to choose the more suitable way. An "entity" can be anything one wishes.

Therefore, in this case, the "entity" is a User. Each property is always associated with one entity. As far as PropertySet is concerned an "entity" has an entity name, and a numeric id.

The id is the same as the id of the propertyentry record for this property. For more information on PropertySet please see its documentation. Also see Jira Database Schema. A Jira application is built on the Jira platform, and extends and modifies the base functionality provided by the Jira platform. For example, the Jira Software application provides software development features that are not part of the Jira platform, such as agile boards, linked development tool information e.

An Application is a blob of plugins that operate together on top of the platform to provide functionality. The plugins can be divided into three types:. An Application may be installed, upgraded, disabled, removed, licensed, and have its configuration cleared dynamically. If you are building for one of the Jira applications, rather than on the Jira platform itself, you will also need to be aware of the following:. A lot of business logic in Jira is implemented in hundreds of java classes.

The classes can be simple utility classes or Manager Objects. Manager Objects in Jira usually have one specific goal or topic. For example com. VersionManager is used to work with project versions, i. Manager objects use a lot of external dependencies, most of which are open source, but some are developed by Atlassian and are usually shared between Atlassian products.

Since Jira 3. The idea is that any validation of business logic necessary is carried out by the service classes whereas manager classes are responsible for actually doing the action.

For instance see the ProjectService's validateCreate method and it's corresponding create method. The ProjectManager then only has a create method which will go off and create a project assuming any validation has already been carried out by the client. This allows clients to simply call the service class in order to validate and create a project, but still gives the flexibility of circumventing validation if the ProjectManager is used directly.

The Atlassian Event library is available to all plugins, allowing them to listen to events occurring within Jira. The events available in Jira are shown below. Cloud Data Center and Server 8. In this section Installing Java. Related content No related content found. Still need help? The Atlassian Community is here for you. No hardware? No problem! Try using Jira applications in the Cloud.

No installation required, get started in 5 minutes Option to migrate to your own server later Choose from a set of supported apps to install. Client-side installation requirements Client-side requirements Browser Enable your browser to execute JavaScript from your Jira applications to access their full functionality.

Memory 2 GB of Java heap size is enough for most evaluation purposes. Database Jira applications come pre-configured with the H2 database, which is suitable for evaluation purposes only, it shouldn't be used in production environments.

For a small number of projects less or equal to with 1, to 5, issues in total and about users, a recent server multicore CPU with 8GB of available RAM and a reasonably fast hard drive rpm or faster should cater for your needs.

See the upgrade notes for more information. Could not load branches. Could not load tags. Latest commit. Git stats 7 commits. Failed to load latest commit information. View code. Jira on Kubernetes These are my rough notes on how to run a single node Jira server using the built-in H2 database. Overview This guide is only showing the high level steps to provision a basic Jira setup This is NOT production ready. Do not run Jira like this in production.