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.
July 11, 2017
Event Payload Filter
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
JIRA
- Auto invite JIRA users to your ML project when their time is entered against a JIRA Issue or Sub-task
- Allow for syncing Mavenlink Tasks at all 5 levels to JIRA Issues if JIRA Sub-tasks are not part of the synchronization definition.
- When a new JIRA Issue is created, the synchronization will create a new ML Task at the top level. It can then be moved to any other level in the project and the synchronization will keep it in sync with its JIRA Issue without moving it from its new location.
- The exception to this is the Sprint scenarios where the level 1 Mavenlink Tasks represent a Board's sprints and backlog. The second level of Tasks represent the JIRA Issues.
April 12, 2017
Log Acknowledgement: 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
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
Integration Platform Exceptions View
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
JIRA
Do you want to map your Jira Bugs and Stories to Mavenlink Issues and Tasks quickly and easily?
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.
January 1, 2017
JIRA
For Agile/Scrum Boards:
- 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.
July 13, 2016
JIRA
Good News: Our JIRA integration has some new features 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 sub-tasks 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 features are options that you can turn on for your existing scenarios using the Integration Platform. For more information, read more here or speak with your Account Executive or Client Success Manager, or email support@mavenlink.com.
