Jira project page

On This Page

Subpages
Manifest example
Properties
Extension data

The jira:projectPage module adds the app in the horizontal tab navigation in Jira.

For Jira Service Management, you can access the app within the Jira Service Management project in the left navigation.

The page URL is constructed in the form of: /jira/{projectType}/projects/{projectKey}/apps/{appId}/{envId}

This module can be used in Jira and Jira Service Management.

For UI Kit 1, see the ProjectPage component documentation for an example. When adding this to your app, use it as a top-level component.

Example of a project page

Example of a project page - JSM

Subpages

By default, the jira:projectPage module registers a top-level page. However, there is an option to register multiple pages using a pages or sections field.

Use pages to add individual pages to the app and sections to group pages.

This will only change the project page URL, you will need to handle routes inside your custom UI app using view.createHistory().

This feature works only with custom UI.

Manifest example

1
2
modules:
  jira:projectPage:
    - key: hello-world-project-page
      resource: main
      resolver:
        function: resolver
      render: native
      title: Hello World!

Properties

Property	Type	Required	Description
`key`	`string`	Yes	A key for the module, which other modules can refer to. Must be unique within the manifest. Regex: `^[a-zA-Z0-9_-]+$`
`resource`	`string`	If using Custom UI or modern versions of UI Kit	The key of a static `resources` entry that your module will display. See resources for more details.
`render`	`'native'`	If using modern versions of UI Kit	Indicates the module uses UI Kit.
`function`	`string`	Deprecated Required if using UI Kit 1	The key of a function module that returns a UI Kit 1 component.
`resolver`	`{ function: string }` or `{ endpoint: string }`		Set the `function` property if you are using a hosted `function` module for your resolver. Set the `endpoint` property if you are using Forge remote to integrate with a remote back end.
`title`	`string` or `i18n object`	Yes	The title of the project page, which is displayed at the top of the page. The title also appears in the horizontal tab navigation in Jira. The `i18n object` allows for translation. See i18n object.
`icon`	`string`		The icon displayed next to the `title`. For custom UI and UI Kit apps, the `icon` property accepts a relative path from a declared resource. Alternatively, you can also use an absolute URL to a self-hosted icon. See Icons for more information. If no icon is provided, or if there's an issue preventing the icon from loading, a generic app icon will be displayed.
`layout`	UI Kit: `native` `basic` Custom UI: `native` `blank` `basic (deprecated)` (default: `native`)		The layout of the project page that defines whether a page is rendered with default controls (native), lays out the entire viewport with a margin on the left and breadcrumbs (basic for UI Kit), or is left blank allowing for full customization (blank for custom UI).
`pages`	`Page[]`	You can only specify `pages` or `sections` but not both.	The list of subpages to render in the app.
`sections`	`Section[]`	You can only specify `pages` or `sections` but not both.	The list of sections to render in the app.
`displayConditions`	`object`		The object that defines whether or not a module is displayed in the UI of the app. See display conditions.

i18n object

Key	Type	Required	Description
`i18n`	`string`	Yes	A key referencing a translated string in the translation files. For more details, see Translations.

Page

Manifest example

1
2
modules:
  <module-name>:
    - key: hello-world-jira-module-page-example
      resource: main
      resolver:
        function: resolver
      render: native
      title: Hello World
      pages:
        - title: page example
          route: page-example-1
          icon: https://example.com/icon.png

Properties

Property Type Required Description

Property	Type	Required	Description
`title`	`string` or `i18n object`	Yes	The title of the subpage, which is displayed on the sidebar. The `i18n object` allows for translation. See i18n object.
`icon`	`string`		The URL of the icon that's displayed next to the subpage title. A generic app icon is displayed if no icon is provided.
`route`	`string`	Yes	The unique identifier of the subpage. This identifier is appended to the project page URL.

title

string or i18n object

Yes

The title of the subpage, which is displayed on the sidebar.

The i18n object allows for translation. See i18n object.

icon string The URL of the icon that's displayed next to the subpage title. A generic app icon is displayed if no icon is provided.

route string Yes The unique identifier of the subpage. This identifier is appended to the project page URL.

Section

Manifest example

1
2
modules:
  <module-name>:
    - key: hello-world-jira-module-section-example
      resource: main
      resolver:
        function: resolver
      render: native
      title: Hello World
      sections:
        - header: example section
          pages:
            - title: page example
              route: page-example-1
              icon: https://example.com/icon.png

Properties

Property Type Required Description

Property	Type	Required	Description
`header`	`string` or `i18n object`		The section header. The `i18n object` allows for translation. See i18n object.
`pages`	`Page[]`	Yes	The list of subpages to render within the app.

header

string or i18n object

The section header.

The i18n object allows for translation. See i18n object.

pages Page[] Yes The list of subpages to render within the app.

Extension data

UI Kit and Custom UI

Use the useProductContext hook to access the extension context in UI Kit or getContext bridge method in custom UI.

Property	Type	Description
`type`	`string`	The type of the module.
`project.id`	`string`	The id of the project where the module is rendered.
`project.key`	`string`	The key of the project where the module is rendered.
`project.type`	`string`	The type of the project where the module is rendered.

UI Kit 1

Use the useProductContext hook to access the context in UI Kit 1.

Extension context

Property	Type	Description
`type`	`string`	The type of the module.

Platform context

Property	Type/value	Description
`projectId`	`string`	The ID of the project where the module is rendered.
`projectKey`	`string`	The key of the project where the module is rendered.
`projectType`	`string`	The type of the project where which the module is rendered.