On this page:
|
Workflows
A Jira workflow may have conditions, validators, or post-functions that refer to other Jira objects, such as:
...
PCJ already supports and handles conditions, validators, and post-functions defined in Jira "out of the box" plus the most popular workflow apps at the Atlassian Marketplace, as explained in Specific Information for Some Object Typesinformation for some object types (see Conditions, Validators, and Post-functions).
...
See section 5 for a detailed explanation of how to create a workflow extension for PCJ.
Dashboard gadgets
When users configure dashboards in Jira, they will add gadgets to it. Each of these gadgets provides some functionality to the dashboard, for example, displaying all issues returned by a filter or statistics for a given category of projects.
...
Section 6 provides an in-depth explanation, with examples, of how to create PCJ extensions for gadgets.
New custom entities
Apps often define new types of entities that do not already exist in Jira, for example, ScriptRunner for Jira offers many convenient features including behaviours. Behaviours let you customize the behaviour of fields in the user interface. A ScriptRunner Behaviour is not a custom field, screen, or workflow; it is a completely new type of object that does not exist in Jira out-of-the-box and only appears if ScriptRunner for Jira is installed in your instance.
...