VBScript Lua
This GSE action creates a new service issue. A common usage of this is to register a callback request.
An example call routing script can be found in A.1 - Example: Create Issue.
Configure action parameters
By double clicking a parameter in the list, you can edit it.
BaseURL Required
This is the ase URL of your Jira Service page, for example: https://my-service.atlassian.net
LoginUser Required
This is the email address of the Jira user you want to authenticate with. Please refer to 1 - Preparations for more details.
LoginToken Required
This is the API Token of the Jira user you want to authenticate with. Please refer to 1 - Preparations for more details.
ProjectKey Required
When you created your Jira service project you defined a 3 character key which is used as prefix in all issue ids, for example "SUP" for your "Support" project.
Summay Required
This is the summary or title of the new issue.
Description Required
This is the description of the new issue.
IssueType Required
This is the type the new issue should be created with. When creating a new Jira service project you can select from many template how the project should look like, what types and states it will. You are also free to add any number of own types and states to your project. This example assumes you used the simple "Support" template and made no changes. This means, that the project has the following possible issue types: New Feature, Support, Developer escalation or Bug.
This GSE action checks the issue type you enter here against the list of available/valid types, which can be modified with the next parameter, if needed.
ValidIssueTypes Required
When creating a new Jira service project you can select from many template how the project should look like, what types and states it will. You are also free to add any number of own types and states to your project. This example assumes you used the simple "Support" template and made no changes. This means, that the project has the following possible issue types: New Feature, Support, Developer escalation or Bug.
If you modified your project you need to set the complete list of valid types here, as the GSE action checks the issue type you enter above against the types in this list.
Configure action exits
Exit 0 (Default)
This exit will be reached when everyhting worked fine and the service issue was created. It is recommmended to name this exit "ok" or "created".
Exit 1
This exit will be reached when there was any kind of problem and no topic has been created. It is recommended to name this exit "failed".
If you reach this exit you can refer to 3.4 - Trouble Shooting to figure what went wrong.
Additional return value (as global variable)
g_sLatestJiraIssueID (string)
This global variable holds ID (in PROJECTKEY-XXX format) of the newly created service issue after the ok (0) exit has been reached.
By Tom Wellige
