Activities

...

The Create Issue activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Assignee (text box editor type) (type: string): enter the assignee name. E.g. "D00018" is the username of the JIRA account that the new created task will be assigned to.  
• Affects Versions (text box editor type) (type: string): enter the affected versions name. E.g. "4.1,4.2" if you need to insert more than one version.
• Business Value (text box editor type) (type: string): enter the value for Business Value field. E.g. 10.
• Components (text box editor type) (type: string): enter the component name. E.g. "Administrator,Agent" if you need to insert more than one component.
• Description (text box editor type) (type: string): enter the description for the new created JIRA issue.
• Description Formatted (text box editor type) (type: string): the input content to be set as the task's description if a binding to a variable is used ($using). If set and if the $using:variable syntax is used, this parameter will take precedence over the Description parameter. For example, the $using:DescriptionString syntax will take the value stored in the DescriptionString variable and will use it as the task's description.
• Due Date (text box editor type) (type: string): enter the due date according to the format: "YYYY-MM-DD". E.g. "2016-01-01" .
• Fix Versions (text box editor type) (type: string): enter the fix versions name. E.g. "4.1,4.2" if you need to insert more than one version.
• Issue Type (combo box control) (type: string): select the text value of the issue type. E.g. "New Feature" if the new created issue is a new feature type of JIRA task.
• Other (collection editor type) (type: string): specify other required Field IDs if they are not found among specified parameters of this activity. E.g field ID: customfield_10900 for a custom required field in JIRA.
• Project Key (text box editor type) (type: string): enter the project key where the new JIRA issue will be created. Use GetProjects activity to obtain the existing JIRA project keys or input directly the project key value. E.g. "FLOWSTER" for the project key.  
• Reporter (text box editor type) (type: string): enter the reporter account. Note: the user account used to connect to JIRA must have 'Modify Reporter' rights in order to create an issue with a specified reporter.
• Story Points (text box editor type) (type: string): enter the story points for the new issue. E.g. 2.
• Summary (text box editor type) (type: string): enter the summary text (title of the issue) for the new JIRA issue.
• Summary Formatted (text box editor type) (type: string): the input content to be set as the task's summary if a binding to a variable is used ($using). If set and if the $using:variable syntax is used, this parameter will take precedence over the Summary parameter. For example, the $using:SummaryString syntax will take the value stored in the SummaryString variable and will use it as the task's summary.

...

Here you will find the example powershell script of the screenshot below:

$credential = get-credential -Message "Please enter Jira credentials:" 
$BSTR = [System.Runtime.InteropServices.marshal]::SecureStringToBSTR($credential.Password) 
$jPassword = [System.Runtime.InteropServices.marshal]::PtrToStringAuto($BSTR) 
$jLogin = $credential.UserName.TrimStart("\") 
$bytes = [System.Text.Encoding]::UTF8.GetBytes("$jLogin`:$jPassword") 
$encodedCredentials = [System.Convert]::ToBase64String($bytes) 
  
$restapiuri = "https://flowster-solutions.atlassian.net/rest/api/2/issue/createmeta?projectKeys=SA&issuetypeNames=Bug&expand=projects.issuetypes.fields" 
$jsonresponse = Invoke-RestMethod -Uri $restapiuri -Headers @{"Authorization"="Basic $encodedCredentials"} -ContentType application/json -method get #-body $body 
$jsonresponse.projects 
$jsonresponse.projects.issuetypes.fields

The Read Only Output variable are the possible output values that the activity will provide:

...

...