ACCESS & AVAILABILITY
This integration is available for purchase in Premier and Enterprise. To get started, please reach out to your Account Executive or Client Success Manager, or email support@mavenlink.com.
Overview
Mavenlink’s Jira integration makes it possible for organizations to automatically synchronize project information between Mavenlink and Jira or Jira Agile. Create Jira issues from Mavenlink and improve issue tracking within Jira , enabling reporting and issue resolution. Project status, logged time, and user communication can be transferred between Mavenlink and Jira on a configurable schedule.
Benefits
The Mavenlink-Jira integration allows project teams to perform project activities in the application of their choice, while relying on either application to accurately present project information. This is useful for software development teams that use Jira for managing engineering stories and sprints, yet also need a unified project delivery solution like Mavenlink with broader project management, resource management, and business intelligence capabilities.
Key Benefits Include:
- Improved communication between team members using different systems
- Increased efficiency by avoiding redundant data entry through bidirectional communication between the two systems
- Improved reliability on the accuracy of information in each system
FUNCTIONAL CAPABILITIES
Mapping Scenarios
- Map Mavenlink Project to Jira Project
- Issues in Jira become Tasks in Mavenlink and vice versa
- Map Mavenlink Project to Jira RapidBoard
- Sprints in Jira become top level Tasks in Mavenlink
- Issues (User stories, Bugs etc.) in Jira become nested Tasks in Mavenlink
- Sub-tasks in Jira become nested Sub-Tasks in Mavenlink
- Backlog Issues come over under a Backlog task in Mavenlink
Actions
- Create and update Tasks and Sub-Tasks / Issues and Stories
- Create and update Comments
- Note: Mavenlink time is booked on a per day basis and no time entry over 24 hours can be booked for a day. This means that Jira time entries larger than 24 hours will come over to Mavenlink broken out in multiple time entries whose hours will add up to the total hours of the Jira time entry.
- JIRA users not in your Mavenlink project are automatically invited to it when their time is entered against a Jira Issue or Sub-task that is synced with the Mavenlink project.
- Capture the Epic, Fixed Versions and Jira Issue ID in custom fields of the corresponding Mavenlink Task.
- Configurable mappings for different Task types (milestones, deliverables, issues, etc.) and Statuses (not started, started, completed).
CONFIGURABLE OPTIONS
- Select the frequency and schedule of your integration synchronization
- Select whether to send time entries from Jira to Mavenlink
- Select whether to include Jira subtasks
- Select whether to include the backlog
- Map specific field value pairs for certain fields (e.g. Task Statuses) between the two systems
- Map Mavenlink Users to Jira Users
AVAILABILITY AND ACCESS
The Jira integration is available to Mavenlink Premier accounts as a Professional Services configuration. To get started, speak with your Account Executive or Client Success Manager, or email support@mavenlink.com. Once the integration has been activated by a Solutions Engineer, configuration takes place through Mavenlink M-Bridge, our integrations and developer platform.
The integration requires that the Jira account is configured to allow remote API connections. This can be enabled by a Jira administrator in General Settings.
The integration requires that the Jira instance be accessible through the web. We can connect to both Jira Cloud and Jira Server. The integration was built using Jira Agile 6.7.12 (https://docs.atlassian.com/jira-software/REST/6.7.12/) so any Jira version supporting this API is supported by our integration.
Field Mappings
Time Entries
| Mavenlink | Direction | Jira Field |
|---|---|---|
| Date Performed | ← | Date Started |
| Time | ← | Time Spent |
| Billable | ← | N/A (user configurable) |
| Notes | ← | Comment |
| Estimate | ← | Original Estimate |
Comments
| Mavenlink | Direction | Jira Field |
|---|---|---|
| User | ← → | User |
| Message | ← → | Message |
Note: Mavenlink Replies are not sent to Jira
Sprints
| Mavenlink | Direction | Jira Field |
|---|---|---|
| Title | ← → | Summary |
| Start Date | ← → | Start Date |
| Due Date | ← → | End Date |
| State | ← | State (Past, Active, Future) |
| Custom Field | ← | Epic |
| Custom Field | ← | Fixed Versions |
| Custom Field | ← | Jira Issue ID |
Issues
| Mavenlink | Direction | Jira Field |
|---|---|---|
| Title | ← → | Summary |
| Description | ← → | Description |
| Time Estimate | ← → | Original Estimate* |
| Due Date | ← → | Due Date |
| State | ← | Status |
| Assignee | ← → | Assignee |
| Custom Field | ← | Epic |
| Custom Field | ← | Fixed Versions |
| Custom Field | ← | Jira Issue ID |
* To pass estimates, time tracking has to be enabled and configured for your Jira project. For more information, refer to your Jira documentation: Configuring time tracking. When not configured properly, the following Jira error will be thrown: "Field 'timetracking' cannot be set. It is not on the appropriate screen, or unknown"
Notes:
- Objects of the above types are created and updated. Deletes are not processed at this time.
- Jira Epics can be synchronized to Mavenlink Tasks on Project based scenarios. Epics do not synchronize to Tasks on Board based scenarios.
- Allow for syncing Mavenlink Tasks at all 5 levels to Jira Issues when the option to sync Jira Sub-tasks is not turned on in the synchronization definition.
- When a new Jira Issue is created, the synchronization will create a new ML Task at the top level.
- You can then move it 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.
- The Jira process for converting Jira issues to sub-tasks and Jira sub-tasks to issues is supported in that the Mavenlink tasks that represent the synced Jira issue/sub-task moves accordingly. Due to this Jira process being a multi step user interfacing process, we cannot support this same functionality going from Mavenlink to Jira if you are using a "two-way" scenario. This means that if you move a Mavenlink task underneath another task, upon syncing, it will not be converted to a sub-task in Jira. If you move a task out from under another task in Mavenlink, the synced Jira sub-task will not become a Jira issue. If you have a need to do this conversion, you will need to do it in Jira.
Related Articles:
Step-by-Step:
