Follow

JIRA Extended Field Support

Overview

By default, certain SDE fields will be mapped to certain JIRA fields when syncing between the two.

As of version 3.2 users can choose to change that default mapping.

Customize Field Mappings

When editing a system-wide JIRA connection, refer to "Custom Fields Mapping" - this is under "Advanced ALM Options". When editing a project level JIRA connection "Custom Fields Mapping" should be under "Advanced Sync Options". This field is where you can set up custom mappings using a JSON dictionary.

The integration allows administrators to map certain JIRA fields to SDE task attribute values using certain macros.

The default mapping is defined as:

{"Summary": "${task_id}: ${task_title}", "Description":"${task_richcontent}", "Labels":"${task_tags}", "Priority":"${task_priority_translated}", "Reporter":"${alm_user}"}

To override this, as an example, you can enter the following JSON dictionary to the "Custom Field Mapping" instead:

{"Description":"${task_richcontent} ${problem_richcontent}", "Custom Severity Field":"${task_priority_translated}", "CustomField2":"My Own Text"}

This would override the default mapping to Jira's "Description" field, but not for "Labels" and "Priority". It would also map a task's priority to "Custom Severity Field" - using the "Custom Priority Mapping", and set the value of "CustomField2" to "My Own Text".

Use a list for fields that have multiple options. For example:

{"Labels":["L1", "${task_tags}", "L2"]}

The list of JIRA field types and supported SD Elements task macros are listed below.

Supported JIRA Field Types:

  • Description
  • Priority
  • Labels
  • TextField - Single Line
  • Text Field - Multi Line
  • Select List - Single Choice
  • Select List - Multiple Choices
  • User Picker (Assignee, Reporter)
  • URL Field
  • Radio Buttons
  • Checkboxes

Available Macros:

Macro Example
business_unit General
application Web application
project Release Q1 2016
context Some project context
alm_user jira_user
id 1-T21
task_id T21
task_title Ensure confidential data is sent over an encrypted channel
task_url http://example.com/bunits/bu/app/proj1/tasks/phase/requirements/1-T21
task_content Confidential data must always be sent over an encrypted channel for a security-sensitive application. Use TLS (Transport Layer Security) version 1.2 to establish a secure channel. Enforce this requirement by explicitly refusing plain-text requests for the login and authenticated portions of an application....
task_richcontent (formatted for JIRA) Confidential data must always be sent over an encrypted channel for a security-sensitive application. Use TLS (Transport Layer Security) version 1.2 to establish a secure channel. Enforce this requirement by explicitly refusing plain-text requests for the login and authenticated portions of an application...

Imported from SD Elements: http://example.com/bunits/bu/app/proj1/tasks/phase/requirements/1-T21

How Tos:

I176: Django

Description

Django does not include its own production-grade HTTP server, and therefore does not provide SSL. To comply with this standard, see the accompanying implementation for your HTTP server software. For example if you are using Apache HTTP Server along with Django, see the documentation on how to enable HTTPS for Apache HTTP Server or SSL/TLS Strong Encryption: How-To.

task_phase requirements 
task_status TODO
task_priority 10 
task_priority_translated Blocker 
task_tags SD-Elements, task-tag1, task-tag2, task-tag3
problem_content Many communication channels can be "sniffed" by attackers during data transmission. For example, network traffic can often be sniffed by any attacker who has access to a network interface. This significantly lowers the difficulty of exploitation by attackers.
problem_richcontent (formatted for JIRA) Many communication channels can be "sniffed" by attackers during data transmission. For example, network traffic can often be sniffed by any attacker who has access to a network interface. This significantly lowers the difficulty of exploitation by attackers.
problem_id  

P216

problem_title Cleartext Transmission of Sensitive Information

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments