Versions Compared

Version Old Version 21 New Version 22
Changes made by

wiki

wiki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Activities

...

  • Base URL (text box editor type) (type: string): enter the URL for the JIRA website. E.g. "https://flowster-solutions.atlassian.net" .
  • Password (password editor type) (type: string): the password for the provided username.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the connection. (This parameter is used only when the user wants to send an encripted password from outside the taskworkflow, for example Flowster Portal).
  • Username (text box editor type) (type: string): the username for the JIRA account.

...

  • 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 workflow 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 taskworkflow'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 taskworkflow'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 taskworkflow.
  • 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 taskworkflow'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 taskworkflow's summary.


A common way to obtain additional information about the parameters required for this activity is provided as helper in this dummy project .

...

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:

...


Create User

This activity creates a new user account in JIRA.

Activity Parameters

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

Parameters:

  • Display Name (text box editor type) (type: string): the Display Name for the new user.
  • Email Address (text box editor type) (type: string): the email address for the new user account. 
  • Name (text box editor type) (type: string): enter the name of the new user account. 
  • Password (password editor type) (type: string): the password for the new user. If left empty, a random password will be generated and assigned to the new user account. 
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the new user. (This parameter is used only when the user wants to send an encripted password from outside the taskworkflow, for example Flowster Portal).

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

  • Output Key (type: string): outputs the key for the new user. 
  • Output Result (type: boolean): outputs the status of the operation. True if succeeded , otherwise False. 

 If you want to display the value of the string output parameters use any logging activity that displays string values. E.g. LogTrackData activity.

 


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables ( E.g.JIRAConnection variable for Connection property) or input directly in the property field ( E.g. "Demo User" value for Display Name property).


NOTE: the username used to create the connection to the JIRA website must have rights to create users. (E.g. the user must have Administrative rights)

Delete Issue

This activity deletes a specified issue in JIRA.

Activity Parameters

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

Parameters:

  • Issue Key Or ID (text box editor type) (type: string): enter the key or id for the issue to be deleted. Use Get Issues activity to obtain the existing JIRA issues keys and ids or input directly the value.  E.g. "FLOW-1200" representing the key of the issue to be deleted. This key of the issue is also visible in JIRA website.   


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables ( E.g.IssueKey variable for 'Issue Key Or ID' property) or input directly in the property field. The value stored in IssueKey variable may be the output of Create Issue or Get Issues activities.

 NOTE: the username used to create the connection to the JIRA website must have rights to delete issues. (E.g. the user must have Administrative rights)


...

Create User

This activity creates a new user account in JIRA.

Activity Parameters

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

Parameters:

  • Display Name (text box editor type) (type: string): the Display Name for the new user.
  • Email Address (text box editor type) (type: string): the email address for the new user account. 
  • Name (text box editor type) (type: string): enter the name of the new user account. 
  • Password (password editor type) (type: string): the password for the new user. If left empty, a random password will be generated and assigned to the new user account. 
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the new user. (This parameter is used only when the user wants to send an encripted password from outside the taskworkflow, for example Flowster Portal).

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

  • Output Key (type: string): outputs the key for the new user. 
  • Output Result (type: boolean): outputs the status of the operation. True if succeeded , otherwise False. 

 If you want to display the value of the string output parameters use any logging activity that displays string values. E.g. LogTrackData activity.

 


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables ( E.g.JIRAConnection variable for Connection property) or input directly in the property field ( E.g. "Demo User" value for Display Name property).


NOTE: the username used to create the connection to the JIRA website must have rights to create users. (E.g. the user must have Administrative rights)

Delete Issue

This activity deletes a specified issue in JIRA.

Activity Parameters

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

Parameters:

  • Issue Key Or ID (text box editor type) (type: string): enter the key or id for the issue to be deleted. Use Get Issues activity to obtain the existing JIRA issues keys and ids or input directly the value.  E.g. "FLOW-1200" representing the key of the issue to be deleted. This key of the issue is also visible in JIRA website.   


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables ( E.g.IssueKey variable for 'Issue Key Or ID' property) or input directly in the property field. The value stored in IssueKey variable may be the output of Create Issue or Get Issues activities.

 NOTE: the username used to create the connection to the JIRA website must have rights to delete issues. (E.g. the user must have Administrative rights)


...

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables ( E.g.JIRAConnection variable for 'Connection' property) or input directly in the property field (E.g. "FLOW-1200" for 'Issue Key Or ID' property).



Update Issue

This activity updates s specified issue in JIRA. Complete only the fields that need update.

Activity Parameters

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

Parameters:

  • Assignee (text box editor type) (type: string): enter the assignee name. E.g. "D00018" is the new assignee for the specified JIRA issue.
  • Affects Versions (text box editor type) (type: string): enter the new 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 new value for Business Value field. E.g. 50. .
  •  Components (text box editor type) (type: string): enter the new component name. E.g. "Administrator,Agent" if you need to insert more than one component.
  • Description (text box editor type) (type: string): enter the new description for specified JIRA issue.
  • Description Formatted (text box editor type) (type: string): the input content to be set as the taskworkflow'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 taskworkflow's description.
  • Due Date (text box editor type) (type: string): enter the new due date according to the format: "YYYY-MM-DD". E.g. "2016-01-01" .
  • Issue Key Or ID (text box editor type) (type: string): enter the key or id for the issue to be updated. Use Get Issues activity to obtain the existing JIRA issues keys and ids or input directly the value.  E.g. "FLOW-1200" representing the key of the issue to be updated. This key of the issue is also visible in JIRA website.   
  • Issue Type (combo box control) (type: string): select the new text value of the issue type. E.g. "Bug" is the new Issue type of the specified JIRA issue .
  • Project Key (text box editor type) (type: string): enter the project key where the specified JIRA belongs. 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 update an issue with a specified reporter.
  • Story Points (text box editor type) (type: string): enter the new value for Story Points field for the desired issue. E.g. 100.
  • Summary (text box editor type) (type: string): enter the new summary text (title of the issue) for the specified JIRA issue.
  • Summary Formatted (text box editor type) (type: string): the input content to be set as the taskworkflow'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 taskworkflow's summary.


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables ( E.g.JIRAConnection variable for Connection property) or input directly in the property field ( E.g. "FLOWSTER" value for Project Key property).


...