Page tree

Versions Compared

Key

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

...

Currently, there are no configurations. To add a new one, press on an ‘Add pipeline configuration’ button.
What we see next is an empty form with some input fields:

Setting mapping fields

FieldJIRA notionStreak notionMust haveCommentExample
Streak API key User API KeyMANDATORYThis field expects an API key which goes with a Streak client. You can learn how to get this key from the Streak site. f9e7e3cb0c48475dbc522e129b657c01
Pipeline name Title of pipelineMANDATORYThis is a name of the pipeline which you would like to synchronise with the JIRA project. Once entered values for select options will be filled data from Streak Pipeline (you will find more about these fields below).Sales
Project keyProject Key MANDATORYThis is a JIRA project that will be synchronised with the Streak’s pipeline. This field expects an existing JIRA project key (all letters in uppercase).For example, there is a project named “Best Kitten Gallery” with the project key “BKG” (w/o quotes). You should use “BKG” (w/o quotes). Once provided the issue type field will be automatically filled in with the list of available issue types.BKG
Issue TypeIssueTypen/aMANDATORYThis field represents an issue type of the issue created from Streak. I.e. if you set this field to ‘Story’ - each issue, created by /jira create command will result in the new issue with the ‘Story’ type.This field is populated with the list of available issue types when you provide the valid project key (see field #2). 
Issue assigneeJIRA User MANDATORY

This is a username of the JIRA user who will be the default assignee of each issue created by JSC. If you don’t know the username of the certain user, you can always get it from the user list. The user list is a popup that appears after pressing an icon next to the input field.

After you find the needed user, just click on a row for the popup to disappear and his username will be automatically assigned to the field. This prevents you from incorrect input. 

 
Issue reporterJIRA User MANDATORYThis field defines the user as an author of each change received from Streak (creating issue, adding comment, assigning issue, performing status transition). StreakConnector
Issue numberIssue KeyPipeline fieldMANDATORY

This field represents the name of the Streak column which will hold the JIRA issue key (in our example it’s JIRA-key). This field can only be set if you provide the valid Streak API key, the pipeline name and choose the column name from the list.

JIRA-key
Issue statusStatusPipeline fieldOPTIONAL

This field represents the name of the Streak column which will hold the JIRA status name. This field can only be set if you provide the valid Streak API key, the pipeline name and choose the column name from the list.

JIRA-status
Issue priorityPriorityPipeline fieldOPTIONALThis field represents the name of the Streak column which will hold the JIRA priority name.This field can only be set if you provide the valid Streak API key, the pipeline name and choose the column name from the list.JIRA-priority
Issue assigneeJIRA UserPipeline fieldOPTIONAL

This field represents the name of the Streak column which will hold the JIRA assignee username. This field can only be set if you provide the valid Streak API key, the pipeline name and choose the column name from the list. 

JIRA-assignee
Issue Linkn/aPipeline field This field represents the name of Streak column which hold direct link to Jira isuue . This field can only be set if you provide the valid Streak API key, the pipeline name and choose the column name from the list.
JIRA-link
Description   Optional description of pipeline 

...