What's new in the OSLC Connect for Jira 2.8.0 release

By Robert Baillargeon | 2/12/2021 | Reading time: 7 min

With each new release, our team strives to provide meaningful and valuable enhancements to our customers. As the Product Owner, I’m excited to share the following highlights of this OSLC Connect for Jira 2.8.0 release.

Search and find any artifacts more easily

Accessing artifacts in Jira should always be a simple task. As a Jira user, you are used to using the Issue Key as the quickest way to find a Jira Issue in an Atlassian Dialog.

Our goal with this release is to blend the ability to quickly find any Jira artifact while operating in the IBM DOORS Next, IBM EWM, IBM ETM, or Polarion ALM OSLC dialogs.

In this 2.8.0 release, your Issue Key will be your gateway to find the Jira Issue to link.

issue key in search dialog-oslc connect for jira-sodiuswillert

We have introduced common Atlassian behaviors to the Search Dialog, and you can see critical artifact details to assure you have the right items.

If the selected artifact is outside your project associations, OSLC Connect for Jira will warn you. (see below)

issue key in search dialog-oslc connect for jira-sodiuswillert-2

For Global Configurations users, OSLC Connect for Jira will hint at the artifact's compatibility in your current configuration.

issue key in search dialog-oslc connect for jira-sodiuswillert-3-b

If you liked our old filter dialogs, do not worry, they are still there. Just use the “search for an issue using filters” option.

Enacting your Process with OSLC

Limit transitions to approved statuses

In our 2.7.0 release, we enabled you to visualize the status of your links.

Enacting your Process with OSLC-oslc connect for jira-sodiuswillert-1

These decorators are valuable to influence the decisions of users, but we knew we could go further.

Prevent a transition to a new state with Validator

Change Management tools are crucial to enacting your processes. Jira Issues provide ownership, states, workflow, and attributes to manage the flow of activities.

However, we know with OSLC that critical data is linked to Jira Issues from the enterprise. The OSLC Connect for Jira 2.8.0 release demonstrates the value of linking in OSLC beyond passive behaviors. OSLC can be actionable!

In this release, we introduce a Jira Validator that uses OSLC links. This Validator enables you to prevent a transition to a new state unless specific properties are met. For example, you can now enforce that users cannot begin implementation work on a requirement until all the requirements are approved.

To use this Validator:

  1. Edit your Jira workflow transition to include our Validator.
  2. Parameterize the behavior you want to enact in the validator dialog.
  3. Publish your workflow.
Enacting your Process with OSLC-oslc connect for jira-sodiuswillert-2-1

The OSLC Connect for Jira 2.8.0 release allows you to impose behaviors that enable the enforcement of your process to support their actions. Below is now the behavior of Jira when we try to transition without approved Requirements.

Enacting your Process with OSLC-oslc connect for jira-sodiuswillert-3

OSLC links are now active participants in your Jira workflows. We look forward to hearing how your teams are leveraging this in your workflows.

Watch how to use Jira Validators in the video below.


Improvement on Security

Security is an imperative of OSLC. We always maintain controlled access to resources and require the authentication and authorization to see remote resources.

More options to manage the Configuration and access to OSLC resource

Earlier this year, a change in browser defaults made the integration of OSLC repositories in different domains (for example, myjira.sodius.com to myelm.sodiuswillert.com) more challenging. The change introduced a new behavior for Cookies and impacted most session Cookies. For OSLC Applications, this had the side effect of making embedded dialogs non-operational.

With this release, OSLC Connect for Jira allows Jira admins to enable OSLC interaction by changing the Cookie settings when your Jira application and targeting OSLC repositories in different domains.

Better control of where your OSLC content is embedded

We know teams want to control where their OSLC content is embedded and from where that information is embedded.

OSLC Connect for Jira now allows Jira admins to leverage their Friend definitions to limit the embedded content to the known OSLC endpoints.

These are implemented by standard Content Security Policy (CSP) headers in the web traffic, and it provides your Jira admin with a simple method to enforce more robust security.

Check out the details in our help documents about configuring Security.

Not an OSLC Connect for Jira user yet?

You can try it free directly from the Atlassian Marketplace. Sign up today and start using OSLC Connect for Jira.

Try it free

Already an OSLC Connect for Jira user? Download the OSLC Connect for Jira 2.8.0 release on the Atlassian Marketplace.

Robert Baillargeon

Robert Baillargeon is the Chief Product Officer at SodiusWillert. Before his role at SodiusWillert, Robert has led engineering and research teams developing systems and deploying tools in the Automotive industry. Robert is a provisional ASPICE assessor and has a Masters of Science degree in Software Engineering from Carnegie Mellon University.

Leave us your comment

Most read articles

Subscribe to our blog

Watch the product demo

OSLC Connect for Jira: integrate Jira with IBM Engineering Lifecycle Management.

Icon_OSLC Connect for Jira_color_144*144px_SodiusWillert_2020_RVB


OSLC Connect for Jira leverages Open Services for Lifecycle Collaboration (OSLC) technology to collaboratively allow linking across design and implementation teams and better manage requirements and compliance.