Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
74:jira_feedback [2019/10/11 07:41] – fnpk | 74:jira_feedback [2019/10/28 08:06] – [Stages config.xml] fnpk |
---|
</code> | </code> |
| |
=== Supported Jira fields ==== | === Supported Jira fields === |
* Description: ''targetType=""'' (Empty) | |
* Text Field (single line): ''targetType=""'' (Empty) | |
* Text Field (multi line): ''targetType=""'' (Empty) | |
* Select List (single choice): ''targetType="selectList-singleChoice"'' | |
* Components: ''targetType="components"'' | |
| |
Be aware: If you choose Select or Component then the user entered values must be configured in Jira. Otherwise the ticket creation will fail. | * Description: ''targetType=_ckgedit_QUOT__ckgedit>'' (Empty) * Text Field (single line): ''targetType=_ckgedit_QUOT__ckgedit>'' (Empty) |
| * Text Field (multi line): ''targetType=_ckgedit_QUOT__ckgedit>'' (Empty) * Select List (single choice): ''targetType="selectList-singleChoice"'' * Components: ''targetType="components"'' Be aware: If you choose Select or Component then the user entered values must be configured in Jira. Otherwise the ticket creation will fail. Other Jira fields are not supported at the moment. === Custom Endpoint === If your Jira REST-Endpiont differs from the standard location, you can specify it. If your link to the Jira-API is for example like ''<nowiki>https://api.example.com/example/api/2/issue</nowiki>'' then you have to specify ''<nowiki>https://api.example.com/example/</nowiki>'' as value for this property. ''__''GESHI_OPEN__property name=__GESHI_QUOT__jira.rest.endpoint__GESHI_QUOT__ value=__GESHI_QUOT__ https://api.example.com/example/" /> __''__ === Proxy === You can specify a proxy server. ''__''GESHI_OPEN__property name=__GESHI_QUOT__proxy.enabled__GESHI_QUOT__ value=__GESHI_QUOT__true__GESHI_QUOT__ />__GESHI_OPEN__property name=__GESHI_QUOT__proxy.type__GESHI_QUOT__ value=__GESHI_QUOT__https__GESHI_QUOT__ />__GESHI_OPEN__property name=__GESHI_QUOT__proxy.port__GESHI_QUOT__ value=__GESHI_QUOT__3128__GESHI_QUOT__ />__GESHI_OPEN__property name=__GESHI_QUOT__proxy.hostname__GESHI_QUOT__ value=__GESHI_QUOT__proxy.example.com__GESHI_QUOT__ /> __''__ === OAuth 2.0 Password Grant === We support also OAuth 2.0 with Password Grant. To configure it there are different properties: ''__''GESHI_OPEN__property name=__GESHI_QUOT__authentication.type__GESHI_QUOT__ value=__GESHI_QUOT__oauth20__GESHI_QUOT__ />__GESHI_OPEN__property name=__GESHI_QUOT__authentication.oauth20.granttype__GESHI_QUOT__ value=__GESHI_QUOT__password__GESHI_QUOT__ />__GESHI_OPEN__!– URL to your OAuth 2.0 Token Endpiont –>__GESHI_OPEN__property name=__GESHI_QUOT__authentication.oauth20.tokenendpoint__GESHI_QUOT__ value=__GESHI_QUOT__ https://example.com/oauth/token" />__GESHI_OPEN__!– OAuth 2.0 Client Id –>__GESHI_OPEN__property name=__GESHI_QUOT__authentication.oauth20.clientid__GESHI_QUOT__ value=__GESHI_QUOTGESHI_QUOT__ />__GESHI_OPEN__!– OAuth 2.0 Client Secret –>__GESHI_OPEN__property name=__GESHI_QUOT__authentication.oauth20.clientsecret__GESHI_QUOT__ value=__GESHI_QUOTGESHI_QUOT__ />__GESHI_OPEN__!– OAuth 2.0 Scope –>__GESHI_OPEN__property name=__GESHI_QUOT__authentication.oauth20.scope__GESHI_QUOT__ value=__GESHI_QUOTGESHI_QUOT__ />__GESHI_OPEN__!– OAuth 2.0 (technical) user –>__GESHI_OPEN__property name=__GESHI_QUOT__authentication.oauth20.user__GESHI_QUOT__ value=__GESHI_QUOTGESHI_QUOT__ />__GESHI_OPEN__!– OAuth 2.0 password –>__GESHI_OPEN__property name=__GESHI_QUOT__authentication.oauth20.password__GESHI_QUOT__ value=__GESHI_QUOTGESHI_QUOT__ /> __''__ === Custom Header === You can set custom header to the Jira-REST-Requests. ''__''GESHI_OPEN__property name=__GESHI_QUOT__authentication.customheader.key__GESHI_QUOT__ value=__GESHI_QUOTGESHI_QUOT__ />__GESHI_OPEN__property name=__GESHI_QUOT__authentication.customheader.value__GESHI_QUOT__ value=__GESHI_QUOTGESHI>_ /> '''' |
| |
Other Jira fields are not supported at the moment. | |
| |
=== Custom Endpoint === | |
| |
If your Jira REST-Endpiont differs from the standard location, you can specify it. If your link to the Jira-API is for example like ''<nowiki>https://api.example.com/example/api/2/issue</nowiki>'' then you have to specify ''<nowiki>https://api.example.com/example/</nowiki>'' as value for this property. | |
<code xml> | |
<property name="jira.rest.endpoint" value="https://api.example.com/example/" /> | |
</code> | |
| |
=== Proxy === | |
| |
You can specify a proxy server. | |
| |
<code xml> | |
<property name="proxy.enabled" value="true" /> | |
<property name="proxy.type" value="https" /> | |
<property name="proxy.port" value="3128" /> | |
<property name="proxy.hostname" value="proxy.example.com" /> | |
</code> | |
| |
=== OAuth 2.0 Password Grant === | |
| |
We support also OAuth 2.0 with Password Grant. To configure it there are different properties: | |
| |
<code xml> | |
<property name="authentication.type" value="oauth20" /> | |
<property name="authentication.oauth20.granttype" value="password" /> | |
| |
<!-- URL to your OAuth 2.0 Token Endpiont --> | |
<property name="authentication.oauth20.tokenendpoint" value="https://example.com/oauth/token" /> | |
| |
<!-- OAuth 2.0 Client Id --> | |
<property name="authentication.oauth20.clientid" value="" /> | |
| |
<!-- OAuth 2.0 Client Secret --> | |
<property name="authentication.oauth20.clientsecret" value="" /> | |
| |
<!-- OAuth 2.0 Scope --> | |
<property name="authentication.oauth20.scope" value="" /> | |
| |
<!-- OAuth 2.0 (technical) user --> | |
<property name="authentication.oauth20.user" value="" /> | |
| |
<!-- OAuth 2.0 password --> | |
<property name="authentication.oauth20.password" value="" /> | |
</code> | |
| |
=== Custom Header === | |
| |
You can set custom header to the Jira-REST-Requests. | |
| |
<code xml> | |
<property name="authentication.customheader.key" value="" /> | |
<property name="authentication.customheader.value" value="" /> | |
</code> | |
| |
==== Stages metamodel ==== | ==== Stages metamodel ==== |