Jira Setup
- Daniel Böcker
To bring up b.jira Setup open “Tell me” and search for “Jira Setup”
If you open the Setup for the first time, you’ll be greeted by our assisted setup wizard. if you’ve already opened Jira Setup please proceed here.
Jira Assisted Setup Wizard
Setting up the connection
Please provide the following information.
Field | Description |
|---|---|
Jira Webservice URL | Replace “YOURJIRAINSTANCE” with the URL of your Jira Instance. For example “cronus.atlassian.net“. |
Jira Username | Enter the Jira username, that will be used for synching the data from Jira to Business Central and vice versa. |
Jira API Token | Enter the API Token for the Jira username. If you don’t have API Tokens setup, please see the following manual. |
Download Project Icon | Whether or not the Jira project icons will be downloaded. If you have many projects, enabling this setting will slow down the synchronization significantly. |
Use Tempo Timesheets | Whether or not you’re using the Jira Add-On “Tempo Timesheets” for time tracking. Find more information here. |
Tempo API Token | The API Token for Tempo Timesheets. If you don’t have API Tokens setup, please see the following manual. |
Click “Test Connection” to validate your settings.
If you are testing the connection the first time, the following warning will appear. Confirm with “Allow Always”.
Defining the integration type
With b.jira you can choose between different integration types for integrating your Jira projects and worklogs into Business Central. The integration type is defined for each Jira Project. The default integration type must be setup in Jira Setup.
Sales integration
With the sales integration, Jira projects are synched to Business Central as Jira projects, no Jobs or alike will be created.
If work / time is logged on those Jira projects within Jira, those worklogs will be synched to the Business Central Jira project and can then be transferred into sales documents and posted. In the next step you may setup a default Line Type and No. for the Sales Document Lines that will be created for the worklogs.
Job integration
With the job integration, Jira projects are synched to Business Central as Jira project, those Jira projects will be transferred into Jobs, so that there is one Job per Jira project.
If work / time is logged on those Jira projects within Jira, those worklogs will be synched to the Business Central Jira project and can then be transferred into a job journal or time sheets. In the next step you may setup the details for posting worklogs etc., please find details below.
Field | Description |
|---|---|
Post Worklogs by | Job Journal - Worklogs will be transferred to the job journal |
Default Line Type | [When posting worklogs directly to job journal] |
Default Line No. | [When posting worklogs directly to job journal] |
Post Job Journal Batch | [When posting worklogs directly to job journal] |
Journal Template Name | [When posting worklogs directly to job journal] |
Journal Batch Name | [When posting worklogs directly to job journal] |
Estimates in Jira Issues will be transferred into job planning lines. | |
Default Job Planning Line Type | The default job planning line type that will be used. You can set a different Line Type per Jira User, Jira Issue Type and Jira Issue. |
Default Job Planning Line No. | The default job planning line no. that will be used. You can set a different Line No. per Jira User, Jira Issue Type and Jira Issue. |
| |
Business Central Job No. Series | The No. Series that will be used for creating Jobs from Jira projects. |
Job Task Start Number | The Start Number for Job tasks that will be created for Jira Issues. |
Job Task Increment | The Increment that will be used for Job tasks that will be created for Jira Issues. |
Bi-directional Project Creation
With b.jira you’re able to create Jira projects based on Business Central Jobs. For those Jira projects you’ll need to provide a number series as well as for the issues that are created.
Initial Synch
In this Step we’ll perform an initial synchronization with your Jira instance. Depending on your Jira instance, this may take some time, so grab a coffee and sit back.
Jira User Settings
When using the sales integration or the job journal posting method of the job integration, you are able to select a different Line Type and No. per Jira User.
If you’re using the time sheet posting method of the job integration you must assign a resource per Jira User.
Custom fields Settings
If you use custom fields in your Jira instance, you can select which fields you want to include in Business Central. You can choose up to 5 Code fields, 5 Text fields and 5 Decimal fields.
Setting up Job Queue Entries
In order to continuously synchronize your Jira instance, create Jobs from Jira projects and synchronize Jobs and Jira Projects, a couple of Job Queue Entries have to be created. In this step you can review and adjust the needed Job Queue Entries.
Jira Setup
Connection
Field | Description |
|---|---|
Jira Webservice URL | The API URL of your Jira Instance. For example “https://cronus.atlassian.net/rest/api/3“. |
Jira Username | Enter the Jira username, that will be used for synching the data from Jira to Business Central and vice versa. |
Jira API Token | Enter the API Token for the Jira username. If you don’t have API Tokens setup, please see the following manual. |
Use Tempo Timesheets | Whether or not you’re using the Jira Add-On “Tempo Timesheets” for time tracking. Find more information here. |
Tempo Webservice URL | The API URL of Tempo. This should be “https://api.tempo.io/4” |
Tempo API Token | The API Token for Tempo Timesheets. If you don’t have API Tokens setup, please see the following manual. |
Synchronization
Field | Description |
|---|---|
Integration Type | The default integration type that will be set in every Jira project. |
Synch. Date Filter | Specifies the DateFormula that is used to calculate the Worklog Date Filter. If none is provided, the default of two years is used. |
Download Project Icon | Whether or not the Jira project icons will be downloaded. If you have many projects, enabling this setting will slow down the synchronization significantly. |
Jira Result Limit | The limit of the Jira results per API call. The default value is 50 and should not be modified, unless instructed. |
Tempo Result Limit | The limit of the Tempo results per API call. The default value is 100 and should not be modified, unless instructed. |
Worklogs
Field | Description |
|---|---|
Default Line Type | Select the default Line Type that will be used in Sales Lines or Job Journal Lines, depending on the chosen Integration type / worklog posting type. Available options are G/L Account, Item, and Resource. This default can be overwritten by Jira User, Jira Issue Type, and Jira Issue. |
Default Line No. | Select the default Line No. that will be used in Sales Lines or Job Journal Lines, depending on the chosen Integration type / worklog posting type. This default can be overwritten by Jira User, Jira Issue Type, and Jira Issue. |
Job Integration
Field | Description |
|---|---|
Job Planning Line | |
Default Job Planning Line Type | Select the default Line Type that will be used in Job Planning Lines. Job Planning Lines will be created for estimates in Jira Issues. Available options are G/L Account, Item, and Resource. This default can be overwritten by Jira User, Jira Issue Type, and Jira Issue. |
Default Job Planning Line No. | Select the default Line No. that will be used in Job Planning Lines. Job Planning Lines will be created for estimates in Jira Issues. This default can be overwritten by Jira User, Jira Issue Type, and Jira Issue. |
Business Central Job Creation | |
Business Central Job No. Series | The No. Series that will be used for creating Jobs from Jira projects. |
Job Task Start Number | The Start Number for Job tasks that will be created for Jira Issues. |
Job Task Increment | The Increment that will be used for Job tasks that will be created for Jira Issues. |
Jira Job Creation | |
Jira Job No. Series | The No. Series that is used when creating a Jira project from a Business Central Job. |
Jira Issue No. Series | The No. Series that is used for Jira Issues when creating a Jira project from a Business Central Job. |
Posting | |
Post Worklogs by | Job Journal - Worklogs will be transferred to the job journal |
Journal Template Name | [When posting worklogs directly to job journal] |
Journal Batch Name | [When posting worklogs directly to job journal] |
Post Job Journal Batch | [When posting worklogs directly to job journal] |
License
Your License information.
Synchronization Status
The date and time of the last successful synchronization by Jira data type. Those dates and times can be reset with the action “Reset Synchronization Status“.
Do not reset the Synchronization Status if not advised to do that by our support team. If you have any issues with your synchronization, please contact us at support@bms-gmbh.com