team/docs/main/integrations-guide/jira.mdx at release-11.10

hanzoai/team

Fork 0

mirror of https://github.com/hanzoai/team.git synced 2026-09-30 01:57:35 +00:00

Files

T

b5f007d35e docs: fix broken path links, anchors, and tab rendering from RST-to-MDX migration (#37433 )

* docs: resolve cross-file anchor mismatches from RST-to-MDX migration

The Sphinx-to-Docusaurus migration converted `:ref:`/`{ref}` links using
naive text-slugification, so anchors that pointed to headings in a
different file (e.g. release-summary tables linking into their
respective changelog pages) were emitted as same-page fragments and
silently resolved to nothing.

Built a label registry from the original Sphinx `.. _label:` / `(label)=`
targets to recover the true source file for each cross-reference, then
rewrote the affected links to point at the correct file + heading
anchor. Fixes 282 broken cross-file anchors, primarily in the mobile/
desktop/server release-summary pages, plus assorted same-page anchor
mismatches caught by re-auditing after the prior admonition/anchor fix.

* docs: manually resolve remaining anchor mismatches after cross-file audit

Hand-verified fixes for anchors that fuzzy-matching alone couldn't
safely resolve (confirmed against actual heading text/context, and in a
few cases against the original RST source, before applying):

- Typos and dropped words carried over from the original Sphinx docs
  (e.g. "bot-acocunts", "auto-follow-all-new-channel-threads" ->
  "follow-all-new-channel-threads").
- Sphinx auto-generated duplicate-heading IDs (#id1/#id3/#id4) resolved
  to their real target headings.
- Numbered-step TOC links in enterprise-roll-out-checklist.mdx that
  dropped the leading "N. " used in the actual heading slugs.
- Push-notification docs pointing at the wrong file entirely
  (environment-configuration-settings instead of
  push-notification-server-configuration-settings).
- SAML "saml-enterprise" label resolved to its true cross-file target
  (authentication-configuration-settings#saml-2-0), recovered from the
  original RST label definition that the automated registry missed
  because it sat after an RST transition marker.
- sso-saml-technical references converted from broken same-page/
  malformed-path anchors to correct page links.

* docs: fix SAML 2.0 anchor slug (saml-2-0 -> saml-20)

github-slugger strips periods rather than hyphenating them, so "SAML
2.0" slugifies to saml-20, not saml-2-0 as previously fixed.

* docs: fix broken path links found during docs/main migration cleanup

* docs: convert div.tab blocks to Docusaurus Tabs/TabItem components

* docs: restore missing Kubernetes deployment architecture diagrams

The RST-to-MDX migration never copied over the AWS/Azure/Oracle
architecture diagrams referenced by the deployment-architecture-at-scale
page, leaving broken images in each Tabs/TabItem.

* docs: fix 7 anchor mismatches from the fragment/heading audit

Covers three root causes from the anchor mismatch breakdown:
- Fragment repeated the target page's own title instead of a real
  heading, so the link is simplified to point at the bare page.
- Heading exists verbatim but lives on a sibling settings page
  (experimental-configuration-settings, push-notification-server-
  configuration-settings) rather than environment-configuration-settings.
- A page path was mistakenly pasted into a same-page #fragment instead
  of being used as a real cross-page link.

* docs: fix 8 anchor slugs that were close but didn't match the real heading

Repoints links whose fragment was a plausible guess (typo, reworded
heading, or wrong section) at the actual auto-generated slug of the
target heading, confirmed by inspecting each target page directly.

* docs: merge split Tabs blocks so tabs render horizontally

The div.tab conversion script split some sibling tab groups into
separate single-item Tabs blocks whenever a stray blockquote marker
sat between them, causing them to render stacked instead of as one
horizontal tab bar. Merges the MySQL/PostgreSQL and Team/Enterprise
Edition tab groups back into single Tabs blocks.

* docs: remove Azure tab and restore Kubernetes deploy content

The Mattermost Operator, Azure, and Oracle platform tabs on the
Kubernetes deployment guide were split across two separate Tabs
blocks (rendering stacked instead of as one tab bar) and all three
tab bodies were empty because the migration never flattened the
original RST include directives. Removes the unsupported Azure tab
and restores the Mattermost Operator and Oracle content from the
pre-migration RST sources as a single merged Tabs block.

* addresscoderabbitreview

* docs: unify Linux/Kubernetes/Containers deploy pages and fix FIPS/STIG placement

Kubernetes and Containers duplicated full install content across a top-level
page (Tabs) and orphaned sidebar subpages that nothing linked to. Reworked
both to follow the Linux page's pattern: shared content on the landing page,
platform-specific instructions live once in their own subpage.

Also removed configure-fips-at-install-time.mdx, which claimed FIPS is
available for native Linux installs — FIPS/STIG in Mattermost is a container
image property (Chainguard-based build), not available outside Docker/
Kubernetes. Consolidated all FIPS/STIG references onto
containers/fips-stig.mdx and pointed the Mattermost Operator subpage (not
Oracle OKE, which doesn't expose image selection) at it.

* docs: fix review findings — image alt text, Important callout markup, typo

- Replace generic alt="image" on scaling diagrams with descriptive text
  identifying cloud provider and user scale.
- Convert raw div.important markup in deploy-containers.mdx to the
  repo's <Important> component, matching usage elsewhere in the file.
- Fix "Matermost" typo in manage-your-display-options.mdx.

---------

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-10 14:50:13 +03:00

276 lines

22 KiB

Plaintext

Raw Permalink Blame History

 ---
 title: "Connect Jira to Mattermost"
 ---
 <PlanAvailability slug="all-commercial" />
 Minimize distractions, reduce context switching between your project management tool and your communication platform by integrating Jira with Mattermost. You control which events trigger notifications including issue creation, field-specific issue updates, reopened, resolved, or deleted issues, as well as new, updated, or deleted issue comments. Create Jira issues directly from Mattermost conversations, attach messages to Jira issues, transition and assign Jira issues, and follow up on action items in real-time, directly from Mattermost channel subscriptions.
 Mattermost supports versions 7 and 8 of Jira Core and Jira Software products, for Server, Data Center, and Cloud platforms. From v3.0 of this integration, a commercial Mattermost license is required for multiple Jira instances with Mattermost configured using Administrator Slash Commands.
 Jira Service Management (formerly known as Jira Service Desk) isn't supported.
 ## Deploy
 Setup starts in Mattermost, moves to Jira, and finishes in Mattermost.
 <Note>
 - Jira Core and Jira Software products, for Server, Data Center, and Cloud platforms are supported, and tested with versions 7 and 8.
 - Jira Service Management (formerly known as Jira Service Desk) isn't supported.
 - From v3.0 of this integration, support for multiple Jira instances is supported with Mattermost Enterprise and Professional plans, configured using Administrator Slash Commands.
 </Note>
 ### Mattermost configuration
 A Mattermost system admin must perform the following steps in Mattermost.
 .  Install the Jira integration from the in-product App Marketplace:
 > 1.  In Mattermost, from the Product menu <img src="/img/ui/products_E82F.svg" alt="Navigate between Channels, collaborative playbooks, and boards using the product menu icon." className="theme-icon" />, select **App Marketplace**.
 > 2.  Search for or scroll to Jira, and select **Install**.
 > 3.  Once installed, select **Configure**. You're taken to the System Console.
 > 4.  On the Jira configuration page, enable and configure Jira interoperability as follows, and then select **Save**:
 >
 > > - Generate a **Webhook Secret** by selecting **Regenerate**.
 > >
 > > <div class="note">
 > >
 > > <div class="title">
 > >
 > > Note
 > >
 > > </div>
 > >
 > > We recommend making a copy of your webhook secret, as it will only be visible to you once.
 > >
 > > </div>
 > >
 > > - **Allow users to attach and create Jira issues in Mattermost**: Enable or disable the user's ability to attach and create Jira issues in Mattermost. When enabled, you must also [install this Jira integration in your Jira instance](#install-jira-integration-in-your-jira-instance).
 > > - **Mattermost Roles Allowed to Edit Jira Subscriptions**: Specify the Mattermost roles that can edit Jira subscriptions to control which Mattermost users can subscribe channels to Jira tickets.
 > > - **Jira Groups Allowed to Edit Jira Subscriptions**: (Applies to older Jira v2.4 or earlier deployments only) Specify the Jira groups allowed to edit Jira subscriptions as a comma-separated list of user group names. Leave blank to allow any Jira user the ability to create subscriptions. The user editing a subscription only needs to be a member of one of the listed groups.
 > > - **Default Subscription Security Level to Empty**: Enable or disable default subscription security level. When enabled, subscriptions only include issues that have a security level assigned when a security level has been included as a filter.
 > > - **Additional Help Text to be shown with Jira Help**: Define any additional help text to display when users run the `/jira help` slash command.
 > > - **Hide issue descriptions and comments**: Show or hide issue descriptions and comments from subscription and webhook messages.
 > > - **Enable slash command**: Enable or disable slash command autocompletion to guide users through available `/jira` slash commands.
 > > - **Display Subscription name in notifications**: Show or hide subscription name in notification messages posted to a channel.
 > > - **Admin API Token**: Set an [API token](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) to get notified for comments and issue creation events, even when the user triggering the event isn't connected to Jira, and set up Autolink. API tokens must be created using an admin Jira account; otherwise, notifications won't be delivered for projects the user can't access, and Autolink won't work.
 > > - **Admin Email**: Set Admin email to get notified for comment and issue created events even if the user triggering the event is not connected to Jira and setup Autolink for Jira plugin.
 .  Run `/jira setup` to start the wizard to configure the plugin. If you wish to set up the plugin manually, then please follow the steps below.
 ### Install Jira integration in your Jira instance
 To enable your users to create and manage Jira issues across Mattermost channels, you must install this Jira integration, as an application, in your Jira instance.
 - For Jira Server or Data Center instances, run the `/jira instance install server <YOUR-JIRA-URL>` slash command in a Mattermost channel as a Mattermost system admin, then follow the steps posted to the channel, replacing `YOUR-JIRA-URL` with your Jira URL. This value must match the Jira server URL you use to log in. Run the `/jira instance uninstall server <YOUR-JIRA-URL>` slash command to uninstall your Jira Server or Data Center instance from your Mattermost instance.
 - For Jira Cloud, run the `/jira instance install cloud-oauth <YOUR-JIRA-URL>` slash command in a Mattermost channel as a Mattermost system admin, then follow the wizard to complete the setup. Run the `/jira instance uninstall cloud-oauth <YOUR-JIRA-URL>` slash command to uninstall your Jira Cloud instance from your Mattermost.
 ### Configure webhooks in Jira
 A Mattermost system admin and a Jira system admin must perform the following steps to configure a single webhook for all possible event triggers, called a firehose, that you would like to be pushed into Mattermost. Mattermost receives a stream of events from the Jira server via a configured webhook, and routes the events to specific channels. A [channel subscription](#manage-channel-subscriptions-in-mattermost) processes the firehose of data, and routes the events to channels based on your subscriptions.
 .  In Mattermost, run the `/jira webhook <YOUR-JIRA-URL>` slash command in a Mattermost channel to get the appropriate webhook URL, replacing `YOUR-JIRA-URL` with your Jira URL.
 .  In Jira, go to **Jira Settings \> System \> WebHooks**. (For older versions of Jira, select the gear icon in bottom left corner, then go to **Advanced \> WebHooks**.)
 .  Select **Create a WebHook**.
 .  Enter a **Name** for the webhook and add the Jira webhook URL you retrieved above in Mattermost as the URL.
 .  Specify the issue events that will be sent to Mattermost channels by selecting all of the following:
 > - Comments: created, updated, and deleted.
 > - Issues: created, updated, and deleted.
 .  Select **Save**.
 ### Manage channel subscriptions in Mattermost
 Mattermost channel admins can set up notifications they want to receive per channel as subscription rules based on the Jira project, event type, issue type. You can also filter out issues based on its value.
 To modify subscription, users must meet the criteria of both the Mattermost user settings and Jira group settings. If you can subscribe channels to Jira events, you can also set up rules; however, you'll only see the projects and issue types you have access to within Jira. If you can't see a project in Jira, it won't be avaialble as an option.
 If your organization's infrastructure is set up such that your Mattermost instance can't connect to your Jira instance, channel subscriptions won't be avaialable. Instead, use [legacy Webhooks](#legacy-jira-webhooks) instead to allow a Jira webhook to post to a specific channel.
 In any channel, run the `/jira subscribe` slash command to configure the following options:
 - Configure what Jira notifications are sent to the current channel.
 - Specify filters including: affects versions, epic link, fix versions, labels, and priority.
 - Specify custom fields including: checkboxes, labels, radio buttons, and select list (single or multiple choice).
 - Review the approximate JQL output generated. This is not guaranteed to be valid JQL and is only shown as a reference to what the query may look like if converted to JQL.
 Run the `/jira subscribe list` slash command to display all subscription rules set up across all channels and teams on your Mattermost instance.
 #### Legacy Jira webhooks
 If your Mattermost instance can't connect to your Jira instance, you won't be able to subscribe Mattermost channels. You'll need to use legacy webhooks instead.
 .  To generate the webhook URL for a specific channel, run the `/jira webhook` slash command, and use the URL output in the **Legacy Webhooks** section of the output.
 .  As a Jira system admin, go to **Jira Settings \> System \> WebHooks**. (For older versions of Jira, select the gear icon in bottom left corner, then go to **Advanced \> WebHooks**.)
 .  Select **Create a WebHook** to create a new webhook. Enter a **Name** for the webhook, and add the Jira webhook URL `https://MATTERMOST-SITE-URL/plugins/jira/webhook?secret=MATTERMOST-WEBHOOK-SECRET&team=MATTERMOST-TEAM-URL&channel=MATTERMOST-CHANNEL-URL` (for Jira 2.1) as the URL.
 > - Replace `MATTERMOST-TEAM-URL` and `MATTERMOST-CHANNEL-URL` with the Mattermost team URL and channel URL you want the Jira events to post to, using lowercase characters.
 > - Replace `MATTERMOST-SITE-URL` with the site URL of your Mattermost instance.
 > - Replace `MATTERMOST-WEBHOOK-SECRET` with the secret generated in Mattermost by going to **System Console \> Plugins \> Jira**.
 For example, if the team URL is `contributors`, channel URL is `town-square`, site URL is `https://community.mattermost.com`, and the generated webhook secret is `MYSECRET`, the final webhook URL would be: `https://community.mattermost.com/plugins/jira/webhook?secret=MYSECRET&team=contributors&channel=town-square`.
 .  (Optional) Set a description and a custom JQL query to determine which tickets trigger events. For information on JQL queries, see the [Atlassian help documentation](https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-search-in-jira-cloud/).
 .  Set which issue events send messages to Mattermost channels, then select **Save**. The following issue events are supported: issues created, issues deleted, and issues updated (including reopened or resolved when the assignee changes).
 By default, the legacy webhook integration publishes notifications for issue created, resolve, unresolve, reopen, and assign events. To post more events, use the following extra &-separated parameters:
 - `updated_all=1`: all events
 - `updated_comments=1`: all comment events
 - `updated_description=1`: updated issue description
 - `updated_labels=1`: updated issue labels
 - `updated_priority=1`: updated issue priority
 - `updated_rank=1`: ranked issue higher or lower
 - `updated_sprint=1`: assigned issue to a different sprint
 - `updated_status=1`: transitioned issed to a different status, such as Done or In Progress
 - `updated_summary=1`: renamed issue
 Here's an example of a webhook configured to create a post for comment events: `https://community.mattermost.com/plugins/jira/webhook?secret=MYSECRET&team=contributors&channel=town-square&updated_comments=1`
 Any previously configured webhooks set up in Jira that point to specific channels are supported and will continue to work.
 ### Manage notifications
 Jira notifications are messages sent to a Mattermost channel when a particular event occurs in Jira. They can be managed as [channel subscriptions](#manage-channel-subscriptions-in-mattermost) in Mattermost, or managed as [webhooks](#configure-webhooks-in-jira) in Jira. Notifications and metadata shown in a channel aren't protected by Jira permissions. Anyone in the channel can see what's posted to the channel. However, if users don't have the appropriate permission, they won't be able to see further details of the issue if they try to access it in Jira.
 When any webhook event is received from Jira, and it matches a notification rule, it posts a notification to the channel. If there are no subscription matches, the webhook event is discarded.
 ## Enable
 Notify your teams that they can [connect their Jira accounts to Mattermost](#connect-a-jira-account-to-mattermost).
 Do more with Jira interoperabiilty as a Mattermost system admin by using the following slash commands:
 - `/jira instance alias [URL] [ALIAS-NAME]` - Assign an alias to an instance.
 - `/jira instance unalias [ALIAS-NAME]` - Remove an alias from an instance.
 - `/jira instance list` - List all installed Jira instances.
 - `/jira instance v2 <YOUR-JIRA-URL>` - Set the Jira instance to process legacy "v2" webhooks and subscriptions (which aren't prefixed with the instance ID).
 - `/jira stats` - Display usage statistics.
 - `/jira webhook [--instance=<YOUR-JIRA-URL>]` - Display the Mattermost webhook that receive JQL queries.
 - `/jira v2revert` - Revert to the legacy V2 jira integration data model.
 ## Use
 Users who want to use Jira interconnectivity must connect a Jira account to Mattermost.
 Once connected, you'll receive direct messages from the Jira bot in Mattermost for Jira activity.
 ### Connect a Jira account to Mattermost
 .  In Mattermost, run the `/jira connect` slash command in any Mattermost channel to link your Mattermost account with your Jira account. Follow the link into your Jira instance, and select **Allow**.
 If you have multiple Jira instances, run the `/jira instance connect <YOUR-JIRA-URL>` slash command instead to connect to a specific Jira instance.
 .  Once connected, run the `/jira help` slash command to see what you can do.
 .  To disconnect a Jira account from Mattermost, run the `/jira disconnect` slash command in any Mattermost channel.
 ### Get started
 Here are some common slash commands you can get started with:
 - `/jira info` - Display information about the current user and the Jira integration
 - `/jira connect [jiraURL]` - Connect your Mattermost account to your Jira account
 - `/jira disconnect [jiraURL]` - Disconnect your Mattermost account from your Jira account
 - `/jira issue assign [issue-key] [assignee]` - Change the assignee of a Jira issue
 - `/jira issue create [text]` - Create a new Issue with 'text' inserted into the description field
 - `/jira issue transition [issue-key] [state]` - Change the state of a Jira issue
 - `/jira issue unassign [issue-key]` - Unassign the Jira issue
 - `/jira issue view [issue-key]` - View the details of a specific Jira issue
 - `/jira instance settings` - View your user settings
 - `/jira instance settings [setting] [value]` - Update your user settings. `[setting]` can be notifications and `[value]` can be `on` or `off`
 #### Create a Jira issue
 Use the `/jira issue create` slash command to create a Jira issue without leaving Mattermost. You can prepopulate the issue's summary by running `/jira issue create This is my issue's summary`. You're prompted to fill out the issue details.
 ![An example of the create Jira issue workflow.](/images/create-jira-issue.png)
 #### Transition Jira issues
 You can transition issues without leaving Mattermost by using the `/jira transition &lt;issue-key&gt; &lt;state&gt;` slash command. States and issue transitions are based on your Jira project workflow configuration. For example, `/jira transition EXT-20 done` transitions the issue key EXT-20 to a `done` state. Partial matches are supported. For example, running the `/jira transition EXT-20 in` slash command transitions the issue to an `in progress` state. However, if your Jira instance includes states of both `in review` and `in progress`, the Jira integration bot will prompt you to clarify which state you want.
 #### Assign Jira issues
 Assign issues to other Jira users without leaving Mattermost using the `/jira assign` command. Partial matches on usernames, firstnames, and lastnames are supported. For example, running the slash command `/jira assign EXT-20 john` transitions the issue EXT-20 to John.
 ## Upgrade
 We recommend updating this integration as new versions are released. Generally, updates are seamless and don't interrupt the user experience in Mattermost. Visit the [Releases page](https://github.com/mattermost/mattermost-plugin-jira/releases) for the latest release, available releases, and compatibiilty considerations.
 ## Frequenly asked questions
 ### How do I disable Jira interoperability?
 You can disable the Jira integration at any time from Mattermost by going to **System Console \> Plugins \> Jira**. Once disabled, any webhook requests coming from Jira are ignored, and users can't create Jira issues from Mattermost.
 ### Why isn't the Jira integration posting messages to Mattermost?
 Try the following troubleshooting steps:
 .  Confirm that your [Mattermost Site URL](/administration-guide/configure/environment-configuration-settings#site-url) is configured, and that the webhook created in Jira is pointing to this URL. To ensure the URL is correct, run the `/jira webhook` slash command, then copy the output and paste it into Jira's webhook setup page.
 .  If you specified a JQL query in your Jira webhook setup, paste the JQL to Jira issue search and make sure it returns results. If it doesn't, the query may be incorrect. Refer to the [Atlassian documentation](https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-search-in-jira-cloud/) for help. A JQL query isn't required when setting up the webhook.
 If you're using legacy webhooks:
 - Confirm the team URL and channel URL you specified in the Jira webhook URL match up with the path shown in your browser when visiting the channel.
 - Only events described in the Legacy Webhook documentation are supported.
 - Use a curl command to make a POST request to the webhook URL. If curl command completes with a `200 OK` response, the integration is configured correctly. For instance, you can run the following command:
 ``` sh
 curl -X POST -v "https://<YOUR-MATTERMOST-URL>/plugins/jira/webhook?secret=<YOUR-SECRET>&team=<YOUR-TEAM>&channel=<YOUR-CHANNEL>&user_id=admin&user_key=admin" --data '{"event":"some_jira_event"}'
 ```
 Replace `<YOUR-MATTERMOST-URL>`, `<YOUR-SECRET>`, `<YOUR-TEAM>`, and `<YOUR-SECRET>` with your setup when configuring the Jira integration. The curl command won't post a message in your Mattermost channel.
 ### Can admins restrict who can create or attach Mattermost messages to Jira issues?
 Yes, Mattermost system admins can disable this functionality by going to **System Console \> Plugins \> Jira** to disable the **Allow users to attach and create Jira issues in Mattermost** option.
 ### How does Mattermost know which Jira issues users can access?
 Mattermost only displays static messages in the channel, and doesn't enforce Jira permissions on viewers in a channel.
 Any messages in a channel can be seen by all users of that channel. Subscriptions to Jira issues should be made carefully to avoid unwittingly exposing sensitive Jira issues in a public channel for example. Exposure is limited to the information posted to the channel. To transition an issue, or re-assign it the user needs to have the appropriate permissions in Jira.
 ### Why must every user authenticate with Jira?
 The authentication with Jira lets the JiraBot provide personal notifications for each Mattermost/Jira user whenever they are mentioned on an issue, comment on an issue, or have an issue assigned to them. Additionally, the integration uses their authentication information to perform actions on their behalf. Tasks such as searching, viewing, creating, assigning, and transitioning issues all abide by the permissions granted to the user within Jira.
 Users will need to temporarily enable third-party cookies in their browser during the Jira authentication process.
 ### What does the error message `'/(name)' not found` mean?
 If you see the error `'/(name)' not found` in Mattermost, disable the Jira integration, check the log file looking for messages that refer to plugins and health check fail, such as `ExecuteCommand`, etc. And consider [enabling debug logging](/administration-guide/manage/logging#how-do-i-enable-debug-logging) to log more verbose error events in the Mattermost system log. Then try re-enabling Jira interoperability and review the log file for clues.
 Debug logging can cause log files to expand substantially, and may adversely impact the server performance. Keep an eye on your server logs, or only enable it temporarily or in development environments, and not production enviornments.
 ### Why do I get a webhooks error?
 If you see a `WebHooks can only use standard http and https ports (80 or 443)` error, it indicates that you're using a non-standard port. Jira only allows webhooks to connect to the standard ports 80 and 443. You need to set up a proxy between Jira and your Mattermost instance to let Jira communicate over port 443.
 ### How do I handle credential rotation for the Jira webhook?
 Generate a new secret by going to **System Console \> Plugins \> Jira**. Paste the new webhook URL in your Jira webhook configuration.
 ## Customize
 This integration contains both a server and web app portion. Visit the [Mattermost Developer Workflow](https://developers.mattermost.com/extend/plugins/developer-workflow/) and [Mattermost Developer environment setup](https://developers.mattermost.com/extend/plugins/developer-setup/) for information about developing, customizing, and extending Mattermost functionality.
 ## Get help
 Customers with a Mattermost subscription can open a [Mattermost support case](https://support.mattermost.com/hc/en-us/requests/new). Community deployments can report a bug by opening a GitHub issue against the [Mattermost Jira plugin repository](https://github.com/mattermost/mattermost-plugin-jira), or visit the Mattermost [peer-to-peer troubleshooting forum](https://forum.mattermost.com/c/trouble-shoot/16) to access the global Mattermost Community for assistance.
 For questions, feedback, and assistance, join our pubic [Integrations and Apps channel](https://community.mattermost.com/core/channels/integrations) on the [Mattermost Community Server](https://community.mattermost.com/) for assistance.
 <Tip>
 Download [this Jira workflows datasheet](https://mattermost.com/mattermost-jira-datasheet/) to learn more about using Mattermost and Jira, including:
 - Key benefits to integrating Jira and Mattermost
 - Common Jira Workflows on Mattermost
 - How to get started with the Jira plugin for Mattermost
 </Tip>

276 lines 22 KiB Plaintext Raw Permalink Blame History

276 lines

22 KiB

Plaintext

Raw Permalink Blame History