General Configuration Jira

Owned by Alexander Wolf
Last updated: Sep 10, 2024
2 min read

Add Custom Field “External Links“

In the Jira Database the oslc Links are saved as custom Field so you first need to add the “External Links“ Field where the olsc are saved.

Jira Administration → Issues → Custom fields → Add custom field → Text Field (multi line)

Field Name: “External Links“

Add that field to All Projects! After that it is most likely that you need to reindex your Jira Database.

 

OSLC Connector for Jira Admin Menu

General Configuration

 

Master Key:

Here you can setup a Master Key which is used to encode your Customer Secrets from the OSLC Adapter

 

Select default behaviour of OSLC Links:

Here you can configure on Project Scope if the OSLC Connector should by default show all OSLC Links or hide them.

General_config.png

Network Configuration

This View is used to turn SSL Configuration on and off. It is highly recommeded to use the “Default Settings” as SSL Parameters. You also can configure the Path to your Trust Store, where you need to import any custom SSL Certificates.

Friends Managment

This View manages the Rootservices URL and Consumer Keys used for Outbound Oauth 1.0 & 1.0a Connections.

Consumers Managment

This View manages the Consumer Key used for Inbound Oauth 1.0a Connections.

Link Type Managment

Here you can define which OSLC Link Types are supported by your Jira Instance.

Default OSLC Link Types are:

name

url

target

Domain

source

Domain

name

url

target

Domain

source

Domain

Implements Requirements

http://open-services.net/ns/cm#implementsRequirement

RM

CM

Verified Requirements

http://open-services.net/ns/cm#testedByTestCase

QM

CM

Relates Requirements

http://open-services.net/ns/cm#relatedChangeRequest

CCM

CM

Affects plan item

http://open-services.net/ns/cm#affectsPlanItem

CCM

CM

Affects Requirements

http://open-services.net/ns/cm#affectsRequirement

RM

CM

Traces Architectural Element

http://smartfacts.com/ns/am#tracedByIssue

AM

CM

Project Association

This View is needed to associate an Jira Project with and OSLC Target (e.g. Smartfacts Warehouse, IBM Jazz Project).

If you are linking Artifacts from Jira to Smartfacts you must configure an project association and enable the Back Link Query because the Links are saved in Smartfacts and Jira needs to fetch Links from Smartfacts.

You can also enable and disable the Back Link Query from Jira to Smartfacts if you don’t need it.

By default you should use genOSLC Back Link Query which is the current Adapter the OSLC Adapter is currently deprecated but should still work on the Smartfacts side.

You can check which Adapter your Smartfacts Instance is using by finding the Rootservices URL (Smartfacts → Model Warehouse Profile → Rootservices → Rootservices File).

Permission Managment

If you want only specifiy user groups of your Jira Instance allow to use the Application you can add User Groups in this Site and give them Read and/or Edit Access.