Once the connection has been established admins and users can create field mappings. Field mapping defines which StorYd Epic field map to which Jira custom field for a particular Jira project and Issue Type. By default, only admins can create field mapping. Navigate to the integration tab on the StorYd Application admin page. For the integration you want to create a field mapping, select the menu icon, and then select “Field Mapping”.
This will open up a full-screen pop where Field mappings can be created.
Allowing non-admin users to create and save mappings
On the admin Field Mapping popup, in the bottom left, there is a setting called “Allow users to create, edit, and save mappings“, enabling this will allow all users to create and save field mapping from the Epic export page.
Defining a field mapping.
In the field mapping popup, once users select a Jira project and Issue type. A “Jira Field” field will be displayed, this is all the fields available for the selected project and Issue type. Jira fields selected and added in this field will be used in the mapping.
Some fields can be added multiple times to allow multiple StorYd Epic fields to be exported into a single Jira field e.g. description.
Once a Jira field has been added to the mapping, for each Jira field added users need to select what StorYd Epic field will map into a particular Jira field
Field Mapping Types
Depending on the Jira field and selected mapped StorYd epic field, users will need to select a mapping type.
Different mapping types will map StorYd Epic data differently into a Jira field.
“Direct”
“Direct“ mapping directly maps the value from the StorYd Epic field into the Jira field. For example, the “Epic Description” StorYd field can directly map into the description field. This will place the text content of the “Epic Description“ into the Jira field.
“Match options to option”
“Match options to option” mapping type is available when a StorYd option field (e.g. priority ) maps into a Jira option field (e.g. priority or select field). This mapping type will select the Jira option that matches the StorYd option. This will match based on the case-insensitive names of each option. Excluding the case, the options need to be an exact match, this includes characters like commas, dashes, etc.
“set options to option”
If “set options to option” type is selected, users will need to select which StorYd options match to which Jira options, selecting the edit icon next to the “set options to option” field to open up a popup.
In the popup select a combination of a StorYd Option and Jira Option and click the add icon to save mapping pari. This will be saved and displayed below the options fields in a list. This list shows what StorYd Options map to which Jira option.
“Range”
If a StorYd number field is selected to map into a Jira option field, users will be able to select a “Range" mapping type. This will allow the users to define different ranges of numbers that map into a Jira option. For example, numbers 0 to 50 will map into the Jira option called “Small size“.
Select the edit icon to open up a popup menu.
In the popup, users can select a range of numbers in the Range field and select a Jira option. Once the add icon is clicked, numbers in the Range field will be mapped to the selected Jira option. A list of Range mappings will be displayed under the Range and Options fields.
The “Max Range” field in the bottom left allows users to increase the max range in the Range Field. By default, users can only select a range between 0 and 100.
“Pre-set Value”
Users can select a StorYd field called “Pre-set Value“ to map into a Jira field. This is not an Epic field but allows users to set a preset value for the Jira field. If a Pre-set Value is selected users will either be presented with a text field or an options field, depending on the Jira field type. Data put into the text field or option selected in the options field will be a pre-set value that will be used to set the Jira field.
Testing a field mapping
Once a field mapping is defined users can test the field mapping using the “TEST MAPPING“ button.
If the field mapping is unsuccessful there will be an error shown in the bottom left and if there are field errors, there will be a list of field errors displayed and a reason why the test failed.
Saving field mapping
If the test was successful you will be able to save the mapping or copy it to another project.
Saving the field mapping will save the current field mapping for the selected project and Issue Type. Once saved, if users navigate back the field mapping for that particular project and Issue Type the saved field mapping will be loaded.
Selecting “Copy to other projects“ will open a popup that will allow users to select specific projects or all projects. Once projects are selected users can select “Start Test“. This will run through all the selected projects and test/save the current field mapping against each project and the currently selected Issue Type (e.g. Epic).