🎫Jira Integration

Work with your Jira backlog in your Metro Retro board.

Jira integration is only available on the Business or Enterprise Plan. For more information about what is included in each plan, read our guide here.

Our Jira integration lets you work with your Jira backlog in your Metro Retro board.

Jira cards can be imported and edited, or new issues can be sent to Jira from your stickies.

Connect your Atlassian account and import your data

Sign-in to Atlassian

To connect your Atlassian account and import Jira cards, use the import option in the Toolbar, by clicking the board name and selecting 'import data', or if you are using one of our Jira 'powered' templates you will see a 'Import From Jira' button on the board.

Sign-in to Atlassian to connect

Select your project

Select and import your project items

Select individual items, or use the top left check-box to select all. Then use 'import' to add the items top your board.

Your Jira cards will now be added and ready to use.

Create Jira issues from sticky notes

To create Jira items from sticky notes:

• Select the stickies you want to export to Jira

• Click the "Save as Jira Issue" button.

• Enter your project ID, then confirm.

• Your stickies will convert into Jira cards and be sent to Jira. Note - you cannot choose the issue type yet, they will be created as the default issue type on that project. Once the Jira card has been created, you can change the issue type from your board. Use Bulk Change on multiple Jira cards.

• Go to Jira to see your newly-created Jira items!

Delete a Jira card

Deleting a Jira card in Metro Retro does not delete the issue in Jira. It only removes the card from your board.

How to enable immediate 2-way sync

The default Jira connection is not a real-time 2 way sync, instead the data is updated each time you import data or refresh your board.

To enable continuous 2-way sync, your Jira admin needs to contact us to get this set up.

Jira Integration Feedback

We need your feedback to know what's missing for your team and how we can improve the Jira integration for you. Talk to us using the support chat in your boards or email us contact [@] metroretro.io.

Data Security when using the Jira Integration

At least one user on a board must be present and connected to Jira with their Atlassian credentials.

Any user with access to a board can view the Jira issues that have been imported, this includes guests.

Only users that have an active connection authenticated through your Organization's Atlassian login can make updates to Jira issues.

Your Jira data is not permanently stored in Metro Retro when imported. Only the Jira issue ID is stored, and each time the board is opened or refreshed, the full payload of issue data is retrieved each time using those issue IDs. This is stored in temporary memory, which is removed once all Atlassian-authenticated users close the board.

Jira integration data security - expand for more detail

Metro Retro <> Jira integration

Why connect Metro Retro to Jira?

Teams can use their Jira data in Metro Retro for a variety of reasons:

• Sprint Planning

• Workload management

• Retrospectives and Sprint reviews

• Task management

• Scoping and planning

• Roadmaps

• Visualisation of workstreams

How does Metro Retro connect to Jira?

Metro Retro uses OAuth 2.0 to connect a Metro Retro user to a Jira user. The user initiates this flow from within Metro Retro. Their active user (e.g. who they are logged in as) will be connected to their Jira account via the Atlassian OAuth 2.0 login flow.

Note: Deqo Software Ltd is our registered company name, we make Metro Retro.

Once the user has logged into their Atlassian profile and agreed to the connection, Altassian provides us with an offline refresh token that we can use to make requests on behalf of that Jira user. If the user wishes to remove this connection, they can do so at any time from their user preferences in Metro Retro.

What can Metro Retro users do with their Jira data?

Users with an active connection to their Atlassian/Jira user can:

• View Projects they have access to

• View and import Issues they have access to

• Create or Update Issues they have access to

Currently, there is no way to delete data in Jira via Metro Retro. This is a design choice we made to prevent any accidental deletion of data. Deleting a Jira Card on a Metro Retro board just removes the link to the issue.

What Jira data is stored in Metro Retro?

Metro Retro stores:

• Issue data that is imported/loaded for 24 hours in a temporary cache. This includes issue metadata as well as metadata about related objects such as assigned users or epics/sprints.

• Issue ids that are imported into boards until they or the board is deleted.

The key point here to understand is that we do not store any data from Jira, except the ID of issues, in our primary databases.

When a user opens a board that has imported Jira Cards (or imports for the first time), the app will request the latest version of these issues from the temporary cache or Jira, assuming the user has a connection to Jira active. If not, the tickets will appear in a placeholder state with no data present.

Can non-authenticated users view Jira data?

Non-authenticated users cannot independently access your Jira data, but if Jira data has been brought into a board they have access to by another authorized user, they will be able to view the data if it’s been loaded into the board. They cannot modify it.

An example:

An employee of your company imports Jira issues into a board, then invites an external guest from outside the company to the board. The guest will be able to view the imported data, but cannot make changes.

Questions & more information

If you have any other questions, please feel free to email [e-mail] with your questions.

Our Security, Terms, and Privacy pages may also be useful.

A user can only authenticate and connect to their Jira instance inside one organization account. If you attempt to connect to your Jira instance in a 2nd organization space, it will fail.