June 2023 Release Notes (22.0.0.0)

New Sale Price Experience from Microsoft  

Job Resource Price functionality was released in April 2023 by Microsoft in the 22nd BC release. 

The Sales Job Price Lists item was added to the Jobs menu for Jira Role Center:

Upon activating the new feature New Sales Price Experience (in Feature management), the existing records of Job Resource Price are transferred to the new table Price List Line (7001) of Sales Job Price List (table Price List Header (7000)). 

Note, that after enabling this feature for all users, it cannot be turned off again.

1. Process Issues First

2. Set up Job Sales Price

3. Process Worklogs

Improvement for Jira Customer Key field

• The Customer Key field on the Customer-Project Links page is now completed with the corresponding value from the Customer Card in case the Customer No. is specified manually:

• The length of the Jira Customer Key field was expanded to max 50 characters. If it is longer than 20 characters, in Customer No. field the first 20 characters will be displayed, according to the BC standard field length (provided that Create Customers Automatically option is enabled and Customer No. Source is Jira Customer Key on Jira Connect Setup).
  
  Note: if the first 20 symbols are the same for Customer No. and Customer Key, an error will appear: “Customer %1 already has a Contact Business Relation with Contact %1.” In this case, you are recommended to have at least one character (among the first 20) that differs between the customer's keys. 
  
  

Suggest Billable lines per Contract type

An ability to suggest billable lines per Contract Type was added:

Project Manager on the Job Card is filled with Project Lead from Jira Project Settings

The Project Manager field, displayed on the Job Card, is now filled with the value of the Project Lead field, taken from Jira Project Settings (in Jira, not in Tempo):

>

Open Errors page enhancement

Dialog messages for the following actions (Open Errors page) leading to empty pages were made more specific:

• Recheck Errors
  
• Approve
  
• Open Card
  
• Open Source
  

Work Date was added to Job Task Worklogs

The Work Date field was added to the Job Task Worklogs page:

Project Key when changed in Jira is now changed in BC

When you change the Project Key field for the Project in Jira, it is also changed in Business Central after importing the Project. This change can be seen on the following pages:

• Customer-Project Links (Project Key field)
• Jobs (No. field)
• Processed Issues (Project Key field)
• Processed Worklogs (Project Key field)
• Job Journal Lines (Job No. field)
  
  Issues created under the Project with the changed Project Key will also have the updated Issue Key:

Note: if you use only Import Issues from the Sync Tasks submenu (omitting Import Projects), an error will occur (Project Key in Jira has changed. First “Import Projects”).

Check for the name change for Resource in Jira and Account in Tempo 

During the sync process, the automatic check was added to see if the Resource name in Jira and the Account name in Tempo were changed (based on the Atlassian account id). The changed names appear in BC accordingly. 

Other UX improvements

• A notification was added for the case when you select a sync period of more than one month, to prevent unintentional changes in the sync period and setup.

• A warning was added when changing the Jira API URL field in Jira Connect Setup:

• The comment was added to the Open Errors log when you want to post a Job with a status other than Open ("The status of the Job [name ]must be Open"):
  
  
• Dialog message for the app registration was improved:
  
• Fields % Completed and % of Overdue Planning Lines were added to the Jobs section of the Job Planning Lines page: 
  
• A tooltip for Edit Data Imported from Jira toggle was improved:
  
  

Work Type Code automatically populated for Monthly Pay and Daily Pay 

The Work Type Code of the Job Task (when specified in the setup (Monthly Pay or Daily Pay)) is now automatically populated on the Job Resource Prices page.

Check for Jira API Token was added

The check for the correct Jira API Token was added (JIRA Connect Setup > Connection). 

When an incorrect Jira API Token is used (e.g. from the wrong Jira instance), the error is displayed after you click Actions > Setup Tasks > Test Connection Jira:

Minor changes

• The Calculate action was removed from Job Task Worklogs due to being redundant

Jira Connector on Atlassian Marketplace

Check out Jira Connector on Atlassian Marketplace.