...
NOTE: the username used to create the connection to the JIRA website must have rights to edit users. (E.g. the user must have Administrative rights)
Get User
This activity retrieves a collection of user information for the existing JIRA account.
Activity Parameters
The Get User activity parameters can be provided by manual inserted values or via IN arguments or variables:
Parameters:
- User Key (text box editor type) (type: string): enter the user key of the user to be returned. Use Get User/Create User/ListUsers activities to obtain the JIRA Users keys or input directly the value. E.g. "demouser" representing the key of the Demo User account. This parameter takes precedence over Username parameter.
- Username (text box editor type) (type: string): enter the existing username. The username for the user is visible in JIRA website.
The Read Only Output variable are the possible output values that the activity will provide:
- Output (type: collection<string>): outputs a collection of user info.
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 'Username' property).
Use the following workflow logic as example to iterate through a variable of type collection<collection<string>>. For more information on how to use Custom ForEach activity please check Workflow link.
- Add a CustomForEach activity of type string to iterate through the UserInfo collection of information.
- Add in the body of the CustomForEach sequence a logging activity, e.g. LogTrackData to display the string value of the Iterator.
Get Issues
This activity retrieves a collection of issues for the existing JIRA account.
Activity Parameters
The Get Issues activity parameters can be provided by manual inserted values or via IN arguments or variables:
...
This activity retrieves a collection of projects for the existing JIRA account.
Activity Parameters
The Get Projects activity parameters can be provided by manual inserted values or via IN arguments or variables:
...
This activity resolves a specified issue in JIRA.
Activity Parameters
The Resolve Issue activity parameters can be provided by manual inserted values or via IN arguments or variables:
...
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 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 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.
- 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 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.
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).
...