Jira Cards allow you to work with Jira issues directly within Miro boards. This allows you to include them in collaborative retrospectives, story sizing, backlog prioritization, story mapping, and other team activities.
Available on: Starter, Business, Education and Enterprise plans;
Jira Cloud, Jira Server (On-Premise) and Datacenter
Available to: team members that are editors on the board
💡 Learn more about Jira Cards:
Jira Cards FAQ
How to set up and to uninstall Jira Cards
How to set up webHook for Jira Cards
Possible issues with Jira Cards and Jira Add-on
How to use Jira Cards
Importing Jira Cards
There are two ways to import Jira Cards to your board:
- Copy the Jira issue URL and paste it on the board; or,
- Click the More apps icon (>> or +)on the Creation toolbar, select Jira, pick one, several, or all issues on the page, and click Add.
First, you need to connect your Jira account with Miro. A dialog box will prompt you to log in to Jira with your individual credentials and authorize the connection.
Click Authorize and log in to your Jira account
You will then see the issues that you have access to.
Jira Cards picker
If a user does not authorize their Jira account, they will not see the assignee avatars and the general look of the card will be different.
The viewer is not a part of the board's team
Creating Jira Cards
You can create Jira Cards right from Miro. At the same time, an issue in Jira is created with all the card fields synced automatically.
There are two ways to create a Jira Card from scratch on the board:
- By using the Jira app in Miro.
- By converting an existing sticky note or card into a Jira card.
- From the Creation toolbar, click the More apps icon (>>or+).
- Choose Jira Cards.
- In the dialog box, click Create issue.
- Fill in the form as needed and click Create.
Creating a Jira Card via the picker
2. Go to the context menu and click the Convert to Jira issue icon
Converting a sticky into a Jira card
⚠️ It’s not possible to convert cards located in USM Tasks line into Jira Cards.
⚠️ During the conversion, tags and Start date (available on Miro Cards) will be lost. Assignee will need to be set anew.
Bulk-convert into Jira Cards
- Select the sticky notes you want to convert
- Click the Convert to Jira issue icon on the context menu
- Select values (issue type, priority, assignee, etc.) on the modal and click Convert. The selected values will be applied to all Jira cards (i.e., if you set bug for issue type, all the stickies will be converted to bugs). The text on the stickies will be passed to the Summary field.
You can convert up to 50 sticky notes at once.
Bulk convert cards into Jira Cards
- Select the cards you want to convert
- Click the Convert to Jira issue icon in the context menu
- Select values (issue type, priority, assignee, etc.) on the modal and click Convert. The selected values will be applied to all Jira cards. For example, if you set bug for issue type, all the cards will be converted to bugs. The card assignee, due date and description will be mapped to the new Jira card.
You can convert up to 50 cards at once.
Bulk conversion of cards into Jira Cards
Viewing and Editing Jira Cards
⚠️ Editing Jira Cards is not supported in the Miro Desktop app, Mobile app and Tablet app
You can view Jira cards in either side view or centered view:
Jira card viewing options
You can edit Jira cards two ways:
- From the card on your Miro board, or
- From Jira itself through the card on your Miro board.
- Choose the card you would like to edit and either double-click it or click on the Edit icon:
Edit button
- In the new pop-up window, you will see your Jira issue. To confirm your changes click Update at the end of the page and close the window.
Updating your Jira card
To change the status of the Jira issue choose the Workflow option:
Editing the status of your Jira issue
From the popup choose the Status and Resolution that you need.
Solving the Jira issue
⚠️ Note that this option supports only the core Atlassian functionality (standard statuses and resolutions). If your workflow is customized via plugins or other methods, they may not be available.
- To edit the Jira card, select a card and click the Source button.
Editing a Jira card -
You will be redirected to the Jira issue page in the next tab. After making changes in the Jira interface your Jira card will be updated automatically.
⚠️ Manual changes are displayed immediately. If you use a script or any other automated procedure to update your Jira issues, such changes may come with a slight delay.
How updates occur
| Jira instance update vs Miro card update | When does the update occur? |
| Update in Jira via OAuth 1.0 | Miro Jira Card is updated immediately via Webhook |
| Update in Jira via OAuth 2.0 | Miro Jira Card is updated upon Miro board connect/reconnect, not more than once per hour |
| Update in Miro | Miro Jira Card is immediately updated and the corresponding Jira issue is updated simultaneously |
Polling occurs at regular intervals not less than 60 minutes, or during Miro board connect/reconnect. During polling, Miro sends a request via a Jira API using each users's token to see if any card/instance data has changed.
Changing a card's color
To change any Jira Card's color, select the card or cards and click fill color from the context menu. If you duplicate the card, the new color will be applied to the copy.
Changing a Jira Card's fill color
Enabling custom fields on Jira Cards
Use our in-app Jira picker to enable custom fields like estimates, tags, sprints, and many others for Jira Cards you use on Miro boards. To select fields to display on cards click Jira > Configure cards.
Choosing fields to display on cards on the board
⚠️ Please note that the Jira fields may vary from board to board as the settings are applied to the current board only. The default fields can not be removed from the picker and from the cards (Assignee, Issue type, Priority, Status) but you can always reset settings to default if you don't want additional fields to be added to the card.
✏️ If some fields are not displayed on the board after you chose them in the picker, it means that:
- a field doesn't have a value to be displayed on the board
- this field is not available for the issue type (e.g.Epic name field is available to Epic issue type only)
✏️ If you can't find a field on the card fields list, it means that:
- that kind of field is not supported by Miro (e.g. color type custom field)
- the field is not associated with your Jira instance. Please see the Atlassian guide for Configuring custom field contexts for more information. Please read Possible issues with Jira cards and Jira add-on.
Search options, JQL search
When choosing an issue, you will always see recent tasks first.
You can change the order of the tasks ranking them by:
- Issue type
- Priority
- Key
- Summary
- Assignee
- Status
The basic search allows you to find issues by keywords.
Advanced search allows you to build structured queries using the Jira Query Language (JQL). You can specify criteria that cannot be defined in the quick or basic searches. For instructions on how to build JQL queries, please see this Atlassian article.
JQL search
✏️ If you have a question about the internal workings of the integration, please check out this FAQ article.
✏️ To learn how to install and configure Jira Cards for your Miro team, check out this guide.
✏️ If you experience issues with the integration (e.g. your Jira Cards do not get updated, you cannot choose a reporter), take a look at this article.