Context parameters are special, context-specific values that can be supplied to your apps. These values are provided via special tokens, which are inserted into the URL properties of your Jira Software modules, specifically panels and actions.
Using context parameters, your Atlassian Connect apps can selectively alter their behavior based on information provided by Jira Software. Common examples include displaying alternate content, or even performing entirely different operations based on the available context.
Context parameters can be used with any UI module that takes a URL property, as specified in your
atlassian-connect.json
descriptor. To use a context parameter, simply insert the corresponding
key name, surrounded by curly-braces, at any location within your URL. The parameter will then be
substituted into the URL as Jira Software renders your UI module.
For example, the URL in the following snippet includes the board.id
and board.type
parameters:
1 2... "modules": { "webPanels": [ { "key": "my-configuration-page", "url": "configuration?id={board.id}&type={board.type}", "location": "jira.agile.board.configuration", "name": { "value": "My board configuration page" }, "weight": 1 } ] } ...
The following table details the list of context parameters provided by Jira Software:
Parameter key | Description | Available for |
---|---|---|
board.id | The ID of the current board. | |
board.type | The type (such as scrum or kanban) of the current request type. | |
board.screen | The screen of the current board. Note that the board.mode parameter was deprecated in favor of this parameter. | Modules that are displayed in multiple board screens. |
sprint.id | The ID of the current sprint. | |
sprint.state | The state of the current sprint. |
The Jira platform provides a number of additional context parameters that Jira Software apps can use. For a full list of these context parameters, see the JIRA Platform Cloud documentation.
Rate this page: