1. Content
| Table of Contents |
|---|
...
Click Edit button and set up a connection to USU and activate default interfaces. It is possible to set up more Interfaces as active at the same time.
USU URL: http://[HOST]/vmweb/services/api/execwf
USU Password is encrypted by runCrypto.bat (from USU).
External User is the user name of the Jira User which is set in the Target System of the Generic Interface in USU. Otherwise the interface calls may be looped.
After you have saved the configuration by clicking on Edit button, you can use the button Test Connection to verify the configuration.
If you want to copy an interface including the mappings, just rename the default interface. The current Default interface will be saved with the new name. At the same time a new Default interface will be created with the default settings (as inactive).
Create an external Jira user in Jira (go to 4.1.2).
Create custom fields in Jira (go to 4.1.3).
...
List of supported field names in the Jira Connector in the Object Issue.
Technical field name | Type | Description |
assignee | Object | Assigned Jira User Object |
assigneeId | Column | |
assigneeName | Column | |
attachments | Collection | Collection of Attachments |
comments | Collection | Collection of Issue Comments |
created | Column | |
creator | Object | |
creatorId | Column | |
creatorName | Column | |
description | Column | |
dueDate | Column | |
estimate | Column | (seconds) |
HTMLdescription | Column | |
inwardLinks | Collection | Collection of Issue Links (inward) |
issueId | Column | |
key | Column | |
labels | Column | |
originalEstimate | Column | (seconds) |
outwardLinks | Collection | Collection of Issue Links (outward) |
parent | Object | Parent of subtask Issue |
priority | Object | |
priorityName | Column | |
project | Object | |
projectId | Column | |
projectName | Column | |
reporter | Object | |
reporterName | Column | |
resolution | Object | |
resolutionDate | Column | |
resolutionName | Column | |
simpleStatusName | Column | |
sitIssueURL | Column | |
status | Object | Issue Status Object |
statusId | Column | |
subTaskObjects | Collection | Collection of Sub Tasks (Issues) |
summary | Column | |
timeSpent | Column | (seconds) |
type | Object | IssueType for this Issue |
typeId | Column | |
typeName | Column | |
updated | Column | |
Valuemation Ticket Link | Column | |
Valuemation Ticket No | Column | |
workflowId | Column | |
Custom Fields | Your custom fields can be used as well. The standard Jira Custom field types are supported. |
List of supported field names in the Jira Connector in the Object Jira Project.
Technical field name | Type | Description |
description | Column | |
key | Column | |
name | Column | |
projectId | Column |
List of supported field names in the Jira Connector in the Object Issue Comment.
Technical field name | Type | Description |
authorFullName | Column | |
body | Column | |
commentId | Column | |
created | Column | |
HTMLbody | Column | |
issue | Object | Issue Object |
issueKey | Column | |
updateAuthorFullName | Column | |
updated | Column |
List of supported field names in the Jira Connector in the Object Jira User.
Technical field name | Type | Description |
Column | ||
username | Column |
List of supported field names in the Jira Connector in the Object Attachment.
Technical field name | Type | Description |
attachmentId | Column | Â |
author | Object | Â |
authorName | Column | Â |
created | Column | Â |
filename | Column | |
filesize | Column | |
issue | Object | Issue Object |
issueId | Column | Â |
mimetypes | Column | |
value | Column | Base 64 encoded content of the attachment |
List of supported field names in the Jira Connector in the Object Issue Link.
Technical field name | Type | Description |
destinationObject | Object | Destination Issue |
sourceObject | Object | Source Issue |
List of supported field names in the Jira Connector in the Object CI´s.
Technical field name | Type | Description |
name | Column | |
status | Column | |
systemName | Column | |
sysType | Column | |
validFrom | Column | |
validTo | Column |
List of supported field names in the Jira Connector in the Object Model Tickets.
Technical field name | Type | Description |
description | Column | |
name | Column | |
status | Column | |
tckShorttext | Column | |
ticketclass | Column | |
ticketNo | Column | |
tickettype | Column | |
validFrom | Column | |
ValidTo | Column |
Recursive Mapping: for some advanced use cases it is possible to use the name this in the case of Mapping of the type Object or Collection. It allows to create a dummy structure in the JSON when it is needed on the USU Side. The depth of the recursion is limited to 10 levels.
8.1 Supported Expressions
Function | Example | Result |
listToCollection | listToCollection("Betroffene Systeme","systemname") | "Betroffene Systeme":[{"systemname":"S-06419236"},{"systemname":" S-06415612"}] |
The function listToCollection also accepts Custom Field ID as a parameter. This can be useful when using multiple Custom Fields with the same name. An example: listToCollection("customfield_10010", "systemname").
...
List of supported fields in the Jira Connector in the Object Issue.
Technical field name | Type | Description |
assignee | Object | Assigned Jira User Object |
description | Column | |
dueDate | Column | |
labels | Column | |
priority | Object | |
summary | Column |