Welcome to the Mavenlink Integrations Changelog! This is where you can see a summary of changes that our Product Development Team has made to our Integrations Platform.
2020
January 29, 2020
Support for Xero OAuth 2 Authentication - Feature Enhancement
Xero has migrated to OAuth 2. You can now create services that connect to Xero apps via OAuth 2.
The Xero OAuth 1 service has been deprecated. Any OAuth 1 service created before December 2, 2019 will continue to be supported until December 2020, but newer OAuth 1 services will not.
2019
November 5, 2019
NetSuite Dynamic Discovery - Feature Enhancement
Oracle now dynamically discovers the WSDL URL for your NetSuite service(s). The URL you previously entered in the Services → WSDL Path field now syncs automatically behind the scenes.
August 12, 2019
Xero Integration - New Feature
Connect multiple Xero services for Xero organizations within the same Xero account, and enable Filter by Project to add Project Filters within a scenario to determine what items are sent to the specified Xero organization. To take advantage of this capability, follow these step-by-step instructions.
April 12th, 2019
New Jira Time Sync Config - Feature Enhancement
Sync your Jira time entries without including the notes the user added in the Jira work log description field. By default, this option is set to 'Yes', thus notes are synchronized with the corresponding Mavenlink time entries. To exclude notes, select 'No' in the new option Include Time Entry Notes on the scenario configuration page.
March 27th, 2019
Scenario Bulk Actions - New Feature
Bulk actions allow you to enable or disable many scenarios for any integration with one click. Use the top checkbox to select or deselect all the scenarios. You can then refine your selected scenarios before selecting the bulk action enable or disable actions from the Bulk Action.
March 27th, 2019
Jira Additional Field Sync - Feature Enhancement
Additional field syncing lets you extend your Jira integration by syncing additional data with Mavenlink. Using this feature, you can share additional business-critical information between Jira and Mavenlink, or override an unwanted out-of-the-box mapping.
For each Jira issue, additional fields can be configured to sync from Jira to the Mavenlink task and task custom fields. Configure this via the Additional Fields section of the scenario configuration page. Detailed information on this new feature can be found here.
March 25th, 2019
Scenario Cloning - New Feature
Copy configuration details from a selected scenario to a new scenario for any integration, including additional fields and mappings.
Important: Be sure to change the key parameters of the new scenario so you don’t have both scenarios processing the same events to the same source and target systems.
For the Jira integration, be sure to change the Mavenlink Project and the Jira Project/Board for the new scenario. Having two scenarios running against the same projects can create duplicate data.
January 24th, 2019
Multiple Jira Accounts - Feature Enhancement
Integrate your Mavenlink account with more than one Jira account. Each Mavenlink project can be synced to a Jira project/board in a different Jira account. To take advantage of this capability, please see step by step instructions here.
2018
December 20th, 2018
Jira Comment Creators - Feature Enhancement
There is now a scenario option to add the Jira username to the synced Mavenlink post. Appended to the Mavenlink post will be the name of the Jira user who made the originating comment on the synced Jira issue. To take advantage of this new capability, edit your Jira scenario and select Yes for the new Include Comment Creators option.
Your newly synced Mavenlink posts should look like the below example, with the commenting Jira user's name appended to the beginning of the comment.
October 16th, 2018
Token-Based Jira Authentication - Feature Enhancement
We now support token-based authentication for our Jira Services. In December, Jira is sunsetting support for user-based credentials when accessing their system via the API. To ensure your integration keeps running smoothly, you will need to edit your JIRA Services on the Integrations Platform to use a token. Quick and easy instructions can be found here.
October 16th, 2018
Jira Components - Feature Enhancement
You can sync Jira Components to a custom field on the corresponding Mavenlink task using the new Additional Fields section of the scenario.
To add a field pair mapping, select the Add Field Pair button.
Select to map the JIRA components to a Mavenlink custom task field of type text or multi-choice.
Note: If a component value is synced that does not exist in the other system, it will not be synced.
Currently, the only additional field we support is components. Look out for a future release where we allow additional fields to be synced.
To remove the field pair mapping, select the '-' button to the right of the pair.
October 10th, 2018
Multiple Flat File Servers - Feature Enhancement
You now have the ability to use different file servers for each of your flat file integration scenarios. For example, if your expense file for import needs to be located on one SFTP file server and your time entry file for export needs to be located on a different SFTP file server, the scenarios can now account for this.
In the Services page, you can now create a Global Account Service for each of your FTP, SFTP and S3 file servers.
For your integration scenario, select which file server type and the name of the file service you want the scenario to use.
August 8th, 2018
Jira Subtask Time Sync Only - New Enhancement
You now have the option to bring Jira subtask time over to Mavenlink without syncing the subtask. The time will be added to the Mavenlink task that is synced to the Jira parent issue.
To take advantage of this new functionality, in your Jira scenario, set the ‘Include Jira Subtasks’ option to ‘No’ and set both the ‘Include Jira Issue Time Entries’ and the new ‘Include Jira Subtask Time Entries’ options to ‘Yes’.
July 23th, 2018
Jira Tempo Token - Feature Enhancement
If you are using the Tempo add-on for Jira, the Mavenlink platform needs to connect to Tempo in order to obtain the name of the user who submitted a time entry. To do this, update your Jira Service definitions with a Tempo token. For guidance on creating a Tempo token, please refer to your Tempo documentation.
If you are not using the Tempo add-on, leave the Tempo Token field blank.
July 19th, 2018
NetSuite Expense Report Approver - Feature Enhancement
We have added the ability to send the Mavenlink expense report approver to a designated custom field on the NetSuite expense report. This allows your finance team to see who on the project approved the expenses.
June 22nd, 2018
Scenario Management - Feature Enhancement
All integration scenarios that are generating errors higher than a 60% error rate will automatically be disabled. In this case, an exception will be logged indicating that the scenario breached the acceptable error threshold and you will receive an email alerting you to the problem. If your scenario has been disabled due to a high error count, you will need to review the errors in the Exceptions page and address them. Once addressed, you can re-enable the scenario.
In the new User Email Settings page of the Platform, you can opt out of receiving this email in the future.
June 11th, 2018
NetSuite Job to Mavenlink Scenario - Feature Enhancement
1) You can now indicate which NetSuite jobs should be synced as Mavenlink projects using a custom checkbox field on the NetSuite job. On your scenario, enter the field id of the NetSuite job custom field in the new field pictured below. For NetSuite jobs that have this field checked, a Mavenlink project will be created. If the field is unchecked, no Mavenlink project will be created.
If this field is not filled out, the scenario will pick up all-new NetSuite jobs and create Mavenlink projects for them as it does today.
2) You can send additional NetSuite job field values to the synced Mavenlink project using the new Additional Fields section of the scenario.
To add a field pair mapping, select the Add Field Pair button.
You can select to map a custom Netsuite job field to a Mavenlink custom project field or a native NetSuite job field to a Mavenlink custom project field. Enter the NetSuite field id and the Mavenlink custom field name.
To remove a field pair mapping, select the '-' button to the right of the pair.
Mavenlink Approved Expense Reports to NetSuite Expense Reports Scenario:
We have added the ability to send your expense receipts to NetSuite. Select 'Yes' on the new Sync Expense Receipts option. Then enter the internal id for the file cabinet folder in NetSuite that you would like the receipts to be copied to.
Note: NetSuite has a maximum allowable size of 10MB. Any receipt that is uploaded to Mavenlink that exceeds this size will fail during sync with an exception stating:
The data you are uploading exceeds the maximum allowable size of 10.0 MB. Please change your selection and try again
|
In this case, the expense will need to be edited and a smaller size file uploaded. The expense report will need to be resubmitted for approval before the integration scenario can pick it up for processing.
May 9th, 2018
Service Management - New Feature
You can now edit your Service definition so if your Jira password changes, just select the Edit button for each of your Jira Services and enter the new password. Your scenarios will automatically pick up the new Service changes.
Some Service definition fields are not editable. These fields are part of the unique identifier for the integration and cannot be changed for an existing integration. If a new Service is created for an existing integration but with a different value for one of these unique identifier fields, the Platform will consider the integration to be new and will treat all objects in the source and target system as new.
March 5th, 2018
Scenario Management - New Feature
Integration scenarios that are generating errors higher than a 40% error rate will be automatically disabled. In this case, an exception will be logged indicating that the scenario breached the acceptable error threshold. If your scenario has been disabled due to a high error count, you will need to review the errors in the Exceptions page and address them. Once addressed, you can re-enable the scenario.
February 15th, 2018
Logs Page - New Feature
The page links of the Logs page were causing performance issues for integrations containing a large number of logs. We have removed the ability to navigate to a specific page using page links and changed the number of logs returned to 100 per page. You can still navigate to a specific page of the logs by changing the page number in the URL (/logs?page=2).
A date and time filter has also been added so you can narrow your search down quickly. The default filter is the last 24 hours.
February 15th, 2018
Events Page - New Feature
A date and time filter has been added so you can narrow your search down quickly. The default filter is the last 24 hours.
February 15th, 2018
Exceptions Page - Feature Enhancement
The calculation for the number of occurrences of an exception was causing performance issues for integrations with a large number of errors of that type. For exceptions that exceed 500 occurrences, we are now showing '500+' rather than calculating out the specific number of occurrences.
2017
August 30, 2017
Jira Due Dates - Feature Enhancement
For the Project and Sprint Two Way scenarios, sending the Mavenlink Task's Due Date to Jira is now optional. To not send the Due Date to Jira, unselect the 'Include Due Date' option on your scenario. For Jira Projects and Boards that do not have Due Date configured on the Issue, this option should be turned off so the Issue Update events to Jira do not fail.
July 11, 2017
Event Payload Filter - New Feature
From the Integration Platform Event page, you can now filter your event listing based on specific text in the event payloads. This allows you to identify all events for a given user, project, task, etc. While only a small part of the payload is visible from the Event page, the filter will search the entire contents of the payloads and return those that contain the text entered in the Payload Filter field.
The event payload contains the data that is used as part of the synchronization. Depending on the system and scenario, the contents of the payload can differ.
Note: The search is a LIKE statement so it is case sensitive and you can use wild cards like %. The text you enter is automatically wrapped in %s so if you enter 'Scott%Smith', it is submitted as '%Scott%Smith%'. For more information on other expressions you can use in your search, click here.
May 16, 2017
New Jira Synchronizations - Feature Enhancement
- Auto invite Jira users to your Mavenlink project when their time is entered against a Jira Issue or Subtask
- Syncs Mavenlink Tasks at all 5 levels to Jira Issues if Jira Subtasks are not part of the synchronization definition.
- When a new Jira Issue is created, the synchronization will create a new Mavenlink Task at the parent level. It can then be moved to any other level in the project and synchronization will keep it in sync with its Jira Issue without moving it from its new location.
- The exception to this is Sprint scenarios where the level 1 Mavenlink Tasks represent a Board's sprints and backlog. The second level of Tasks represents Jira Issues.
April 12, 2017
Log Acknowledgement - New Feature
This rarely used feature is being replaced as it was causing performance issues on the Platform. In its place is a new indicator in the menu bar when there has been one or more new exceptions since the last time you visited the page. The exceptions are ordered with the latest at the top so you can see right away which new issues need to be addressed.
March 10, 2017
Mapping Sets - Feature Enhancement
You are no longer able to delete a mapping set if it is being used by an integration scenario. We had instances of customers with invalid scenarios running and generating errors since they had unknowingly deleted a mapping set that the scenario was using. You will now need to update any scenario to use a different mapping set before you will be allowed to delete one.
March 6, 2017
Exceptions View - New Feature
The Exception View is a new way of reviewing your integration errors that allows you to quickly identify what the issue is, possible resolution and re-emit all the related failed events once a resolution has been applied. Each Integration’s events and logs are now grouped by the error message so that once that error is addressed, all events can be processed again using the Re-emit button for the exception. Previously, the error message was buried as one of the many event logs for each event that failed. Now it is surfaced as the exception and all events and logs related to it are linked and therefore viewable in its context.
The number of events that failed due to an exception is found in the Occurrences column. To drill down to the logs and events that failed, click View for the given exception.
Once you have addressed the issue that caused the error, you can select the action to re-emit all the events that failed. For exceptions that can be ignored, you can dismiss the exception. Selecting Dismiss will only remove the exception from the view. The related events and logs are removed.
To have the Exception View turned on for your Integration Platform account, please email support@mavenlink.com.
February 17, 2017
Mapping Jira Bugs and Stories - Feature Enhancement
You no longer need to create separate mapping sets and scenarios for your Mavenlink Issues vs. Tasks. Now you can have one Type Mapping Set and one Status Mapping Set that contain all your Issue Type Statuses as well as your Task Type Statuses and your scenarios will use the correct status during synchronization.
What do you need to do to take advantage of this new enhancement?
If your current scenarios are working as desired, you’re all set. If you are creating new scenarios, you can update your Status Mapping Set to include both Task and Issue Statuses. Your scenarios using this Mapping Set will work for all Tasks, Milestones, Deliverables and Issues. You will notice in the Status Mapping Set, you can now easily see which statuses are specific to Mavenlink Issues.
2017
January 1, 2017
Jira Agile/Scrum Board Synchronization - Feature Enhancement
- We have a new Scenario called “Board - Sprints - 1 way” that allows you to push all your Scrum Board activity to your corresponding Mavenlink Project. Sprints and Backlogs are captured as parent tasks in your Mavenlink project. Additional project work can be managed in Mavenlink and this work is kept out of your Jira project.
- The start date of a Sprint is reflected in your Mavenlink project.
- When a Sprint is closed in Jira, Mavenlink is updated accordingly. The Sprint is marked complete and tasks not done are moved to the Backlog or next open Sprint.
- The Epic that your Issue is assigned is captured in the corresponding Task using a Mavenlink custom field. Insights reports allow you to analyze the time spent per Epic.
2016
July 13, 2016
Jira Updates - Feature Enhancement
Good News: Our Jira integration has some new enhancements that will help you improve your collaboration between your teams and give your project managers more visibility into the work being done in Jira.
For both project- and board-based integrations:
- Jira subtasks can now be captured in a Mavenlink subtask and kept in sync.
- Time logged in Jira can now be captured as time in the corresponding Mavenlink task.
- Comments made in the Jira Issue and Subtask are captured as posts in the corresponding Mavenlink task. Posts made in the Mavenlink task are then copied to the Jira Issue and Subtask so two-way communication is completely coordinated.
- Fixed Versions and Jira ID for your Issues can now be captured in the corresponding Mavenlink Tasks using Mavenlink’s custom fields.
For Agile/Scrum Boards:
- We have a new Scenario called “Board - Sprints - 2 way” that allows you to keep your Scrum Board in sync with your corresponding Mavenlink Project. Sprints and Backlogs are captured as parent tasks in your Mavenlink project.
- The start date of a Sprint is reflected in your Mavenlink project.
- When a Sprint is closed in Jira, Mavenlink is updated accordingly. The Sprint is marked complete and tasks not done are moved to the Backlog or next open Sprint.
- The Epic that your Issue is assigned to can now be captured in the corresponding Task using a Mavenlink custom field.
All of these new options can be turned on for your existing scenarios via the Integration Platform. For more information, read here, speak with your Account Executive or Client Success Manager, or email support@mavenlink.com.
