User Tools
jira_additional_mapping_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
jira_additional_mapping_guide [2017/11/08 14:28] jackson.davenport cleanup priority |
jira_additional_mapping_guide [2018/10/31 16:33] (current) jackson.davenport add details for epic |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| The output is not too readable as is but you can easily pass it into a JSON beautifier tool. Here is an example for the ServiceNow Identifier: | The output is not too readable as is but you can easily pass it into a JSON beautifier tool. Here is an example for the ServiceNow Identifier: | ||
| - | <code json> | + | <code javascript> |
| { | { | ||
| "id": "customfield_11201", | "id": "customfield_11201", | ||
| Line 42: | Line 42: | ||
| https://example.atlassian.net/rest/api/2/priority | https://example.atlassian.net/rest/api/2/priority | ||
| - | <code json> | + | <code javascript> |
| [ | [ | ||
| { | { | ||
| Line 100: | Line 100: | ||
| Here are some example transitions from "To Do" | Here are some example transitions from "To Do" | ||
| - | <code json> | + | <code javascript> |
| { | { | ||
| "expand": "transitions", | "expand": "transitions", | ||
| Line 166: | Line 166: | ||
| Here are some example transitions from "In Progress" | Here are some example transitions from "In Progress" | ||
| - | <code json> | + | <code javascript> |
| { | { | ||
| "expand": "transitions", | "expand": "transitions", | ||
| Line 262: | Line 262: | ||
| </code> | </code> | ||
| + | ===== Mapping Over Epic ===== | ||
| + | The "Epic Link" field on Jira is stored/processed in a different way relative to some of the other fields. The Epic Link is a custom field which may vary between Jira instances. So you will want to check first to verify what this field is. | ||
| + | |||
| + | You can do this by pulling up the fields from the REST API, similar to the custom fields. You do this by appending **/rest/api/2/field** to your URL, ([[https://example.atlassian.net/rest/api/2/field]]). If you take the output of that and put it through a JSON Formatter you should see something like the following: | ||
| + | |||
| + | <code javascript> | ||
| + | { | ||
| + | "id": "customfield_10008", | ||
| + | "key": "customfield_10008", | ||
| + | "name": "Epic Link", | ||
| + | "custom": true, | ||
| + | "orderable": true, | ||
| + | "navigable": true, | ||
| + | "searchable": true, | ||
| + | "clauseNames": [ | ||
| + | "cf[10008]", | ||
| + | "Epic Link" | ||
| + | ], | ||
| + | "schema": { | ||
| + | "type": "any", | ||
| + | "custom": "com.pyxis.greenhopper.jira:gh-epic-link", | ||
| + | "customId": 10008 | ||
| + | } | ||
| + | }, | ||
| + | </code> | ||
| + | |||
| + | Where the id **customfield_10008** represents the field name for Epics. | ||
| + | |||
| + | Similarly if you have two records where TEST-100 is the Epic and TEST-101 is a Story of this Epic - you should be able to access the REST API for TEST-101 ([[https://example.atlassian.net/rest/api/2/issue/TEST-101]]). This shows (amongst all the other fields) your issue, the epic issue, and the corresponding field name. | ||
| + | |||
| + | <code javascript> | ||
| + | { | ||
| + | "id": "49021", | ||
| + | "self": "https://perspectium.atlassian.net/rest/api/2/issue/49021", | ||
| + | "key": "TEST-101", | ||
| + | "fields": { | ||
| + | . | ||
| + | . | ||
| + | . | ||
| + | "customfield_10008": "TEST-100", | ||
| + | } | ||
| + | } | ||
| + | </code> | ||
| + | |||
| + | So when mapping to this field you will want to update your SIAM Mapping to write to this field and pass in the corresponding issue number of the Epic (example: TEST-100). You will need to pass the issue number of the epic, __not__ the unique identifier (49022). | ||
jira_additional_mapping_guide.txt ยท Last modified: 2018/10/31 16:33 by jackson.davenport
Page Tools
