Jira Plugin Updated to Streamline User Integration with Spira | Inflectra

Jira Plugin Updated to Streamline User Integration with Spira

4-Dec-2019 by Inflectra Product News

We are pleased to announce the release updated versions of our Atlassian Jira plugin for cloud and server that simplifies the integration of the two systems and makes the data mapping of users easier. In addition, we have separated out the Jira cloud and server documentation to make setup of the plugin easier.

 

 

Background

When we first released our Jira plugin, we had a single documentation page and plugin for both the Jira cloud and server versions. This was possible because the Atlassian API was the same for both versions of Jira.

However earlier this year, Atlassian made some changes to the Jira API to better comply with data privacy rules and the EU General Data Protection Regulation (GDPR). These changes only affected the Jira Cloud platform. This, together with some other changes to the Jira Cloud and Server APIs means that going forward we will be treating them as two separate products (Jira Cloud and Jira Server) with different documentation and plugins.

Updating Spira Documentation

We have updated our Spira Documentation website (known as Spira Doc) to have separate pages for Jira Cloud and Jira Server:

In addition, we have separated out the downloads page to have two separate plugins:

If you are using the Inflectra Cloud Data Synchronization Service, then you are already using the latest Jira Cloud plugin automatically.

Changes to the Jira Cloud User Mapping

One side-effect of the GDPR changes was that it is no longer possible for Spira to be able to get a user's profile from the Jira Cloud API unless each user has explicitly granted it.

That means, when you map users in Spira to Jira Cloud, you have two choices:

  1. You can map the Spira user to the Jira login name / email address, but this means the Jira email address must be publicly visible:

  2. You can map the Spira user to the Jira Atlassian AccountID, but this is usually a less meaningful identifier. However it will work in all cases:

The good news is that you can mix and match the two approaches. You can have some users map to (1) and some users map to (2) and the synchronization will work just fine.