Configuring Additional Fields for Jira

Follow these steps to configure and sync Additional Fields for both new and existing scenarios:

How to Sync Additional Jira fields for an Existing Scenario

1. Go to M-Bridge, login and navigate to your Jira integration settings.

   

2. In the scenario listing, find the existing, active Jira scenario you want update and select Edit from the Sync drop-down menu.

   

3. From the Edit Scenario page, scroll down to the Additional Fields section and click the Add Field Pair button.

   

4. From the drop-down menu, select Jira Field to Mavenlink Standard Task Field.

   

5. In the Mavenlink drop-down menu, select the appropriate standard task field.
6. Open a new browser tab and navigate to your Jira instance.
7. The fastest way to access your Jira Custom fields is to go here: https://<yourdomain>.atlassian.net/secure/admin/ViewCustomFields.jspa and change <yourdomain> to the domain of your Jira instance. For example: acmecompany.altassian.net/secure/...
   - or -
   You can go to your Jira Settings > Issues > Fields > Customfields
8. Use the search function to locate the Jira Custom field you want. Remember that the fields must be of a compatible type, so a date field must match to a date field, a text field to a text field, integer field to a number or currency field, and so on.

   

9. Highlight and copy the name of the Jira Custom field, and go back to the tab you have open to M-Bridge.
10. Paste the Jira Custom field into the Jira field in M-Bridge.
11. To add another field pair, click the Add Field Pair button and repeat the steps. Do this for all the Additional Fields you want to map to the Scenario.
12. Remove a Field Pair by clicking the remove button.

    

13. When you’re finished, click Save Scenario.

How to Sync Mavenlink Custom Task Fields

To access custom fields in Mavenlink, go to Settings > Custom Fields.

1. Before you begin, you need to create a Task-type Custom Field set in Mavenlink. First, hover over Settings in the left navigation and select Custom Fields.
2. Click Add Custom Field Set.

   

3. Select Task and add a Set name. We recommend naming this something recognizable like “Jira Custom Fields” or “Jira Sync” since you’ll need to select these fields in M-Bridge later on.
4. Click Add. Your set will appear under Project Sets in the list.
5. Now, you'll need to create a custom field in the set. Later, you’ll add this custom field to your project in Mavenlink. Start by opening the Project Set you just created.
6. Click the Add Custom Field button.

   

7. Select a Field type, and enter a Field name. Remember to use a name that you’ll be able to remember when you set up the integration, and that the fields need to match, so if you are syncing a Jira date field, create a Date custom field in Mavenlink.

   

8. Click Add.
9. Repeat for each Field type you want to add.
10. Now go to M-Bridge, login and navigate to your Jira integration settings.

    

11. Edit an existing Jira Scenario, scroll to the Additional Fields section and click the Add Field Pair button.

    

12. From the first drop down menu, select Jira Field to Mavenlink Custom Task Field.

    

13. Under the dropdown menu for Mavenlink, select the appropriate Custom Task field, which are the fields you created in Mavenlink’s Custom Fields.

    

14. Follow the same steps you did for Jira Field to Mavenlink Standard Task Field to copy and paste the Jira Custom fields you want.
15. To add another Field Pair, click the Add Field Pair button and repeat the steps. Do this for all the Additional Fields you want to map to the Scenario.
16. Remove a Field Pair by clicking the remove button.

    

17. When you’re finished, click Save Scenario.

Two-Way Scenarios

In a two-way scenario, standard mapping overwrites Additional Fields added as Jira Field to Mavenlink Standard Task Field. This means the initial sync between Jira and Mavenlink works as it should. However, when Mavenlink syncs back to Jira, standard mappings apply.

For example, if you have a Jira Issue called Billboards and create a Jira Field to Mavenlink Standard Task Field that maps the Mavenlink Title field to a Jira Change reason field, it will update as expected on the initial sync.

What you see in Jira:

What you see in Mavenlink: 

However, when Mavenlink syncs to Jira, the title updates the Jira Change reason, changing it from Billboards to Maintenance.

What you see now in Jira:

What you see now in Mavenlink:

If you decide to setup Additional Fields for a two-way sync, be aware of what fields you map to what so you don't overwrite ones you don't want to overwrite.