Mappings and Naming Conventions for Jira Tasks and SubTasks

Any project you make in Jira will always map to a project in BigTime, and vice versa. Aside from this, however, there are a few different scenarios when it comes to mapping for other fields. This article will show you what those scenarios look like in your Jira connectivity settings.

NOTE: To get to your Jira connectivity setup window, go to your main navigation bar and click MY COMPANY…INTEGRATIONS. Then, click the JIRA tile, and click the MANAGE hyperlink.

Your Jira task and subtask mapping can look like this:

Or:

Once you've set up your mappings, you can select name formats for your tasks. In the TASK NAME FORMAT field, you can select the format for how your Jira tasks will be named in BigTime. These options are:

As an example, let's say you have an issue in Jira that you want to map to a task in BigTime. The "summary" (or name) of the issue is Skills Tracking, and its ID is LPL-8604. Here's how that info would map to BigTime following each of these task name formats:

• Name: Skills Tracking
• ID: LPL-8604
• Name-ID: Skills Tracking - LPl-8604
• ID-Name: LPL-8604-Skills Tracking

If you want your task names in BigTime to always reflect the name you choose for them in Jira, you can check the box labeled ENFORCE JIRA NAMES IN BIGTIME. Checking this box means that even if you edit the name of your task in BigTime, those changes will be overwritten to match whatever is in Jira when you run a sync.

To learn more about how Jira integrated with BigTime, take a look at some of the following articles:

• FAQ: Jira Integration
• How To Integrate With Jira
• How To Sync With Jira