Rate this page:
These design guidelines relate to the new Jira issue view, which is currently only available to some Jira Software users. New modules and extension patterns on this page only relate to Jira Software right now, but we'll be adding them to Jira Service Desk in the near future.
As an app developer, you can define multiple issue context modules in your descriptor, but Jira will only display the first issue context module returned (after any conditions have been evaluated). We recommend you avoid selecting conditions that result in more than one issue context panel appearing on an issue.
If your app has multiple entities you want to represent using issue context panels, you can make use of conditions. For example, if you're building a Git integration, you might want to show related commits, branches, and pull requests for an issue.
In this example, you could define an issue context module in your descriptor for each of these:
You could then make use of conditions to validate against properties that you store against the issue to choose the issue context panel to be displayed.
For each panel you could use a predefined condition, like
entity_property_equal_to. You could then define the condition to decide which panel to display.
'git_integration_display_context_panel === commits'
'git_integration_display_context_panel === branches'
'git_integration_display_context_panel === pull-requests'
Your app may want to have an experience where you want users to take an action before you display an issue context panel. You can define multiple panels to create this experience.
For example, through using conditions and app properties, you could define an issue context panel that prompts users to "Link a conversation".
When a user clicks your panel, you could use the modal dialog target to design a view where the user links a conversation to the issue through your app.
Once a conversation is linked, you could use conditions and app properties to change your panel to communicate that a conversation has been linked.
Rate this page: