Features
Subscription Module
We have developed the Subscription Module to monitor customers' subscriptions and correspondingly bill the usage of Jira Connector.
For a detailed description, refer to the Subscription Module page of our knowledge base.
Collection of Data for Billing and Counting Totals
The procedure was implemented to count the number of active users and worklogs imported to be stored as metrics in the database.
Job Queue
The Job Queue was set up to automate the Sync All process.
Recheck Errors
The Recheck Errors functionality was improved to handle errors with issues and worklogs.
Automated Matching of Atlassian Account IDs
Atlassian account IDs from Jira are now automatically assigned to the already existing Resources in BC.
If a Resource with the same name but without indicated Atlassian Account ID already exists in BC and has a Blocked status, you will be notified of the necessity to unblock this Resource and restart the sync process.
Also, see Resources: Set Atlassian Account ID.
Connect Setup
- Auto Create Billable Planning Lines
You can choose to automatically create billable lines after processing the worklogs. Use the toggle to switch this option ON or OFF as required.
- TnM Job Task No.
A new field TnM Job Task No. was added (Job section of Jira Connect Setup)
The value of this field is used as the name of the Task that will be created during the suggestion of billable lines per Job/Customer/Person Responsible/Project Manager. This Task will contain all billable lines for the Job:
Reverse Job Ledger Entries
A new action was added to make adjustments for the Planning Lines in case Job Journal Lines were posted wrongly with Line Type Budget. Planning Lines follow the Line Type from the Job Journal Line and if it is Budget, it is impossible to create a Sales Invoice.
Click the Reverse Job Ledger Entries action to select the necessary Planning Lines for adjustments.
Two lines will be created: the negative one – the adjustment for the Job Ledger Entry and the Budget Planning Line, and another line with the Billable type (Line Type should be blank), it will generate a Planning Line with the type Billable after Job Journal Lines posting.
The billable line proposed in this case upon clicking on Suggest Billable Lines will have Qty = 0:
>
HTTP Log Functionality
The options Enable HTTP Log and Enable Log HTTP Errors were added for convenient handling of HTTP request status codes.
You can enable/disable it in Jira Connect Setup whenever required.
Call the page from Actions > Setup > HTTP Request Log
The HTTP Request Log page contains the following fields:
- “Request URL” (the URL of the triggered API)
- “Response content” (JSON data from JIRA API)
- “Request Completed Date/Time” (date/time when the request was called)
- “HTTP Status Code” (the HTTP error/success code and line is red if an HTTP error occurs)
- “User ID” (the user who called API URL)
.
Technical Changes
Since the submitted AppSource applications require using a 70-million object range and the reserved Global Mediator IDs, the following was changed:
- The ID of the App
- IDs of Objects
- Prefixes of Objects
The registered affix became GMPJC.
Business Logic Changes
Time & Material
- Ability to suggest billable lines for Time & Material and Time & Material Detailed contract types when the Auto Create Billable Planning Lines option in Jira Connect Setup is disabled
- New fields Worklog ID and Worklog Hours were added to Job Billable Proposal Lines:
For a detailed description of the Time & Material Contract Typer, refer to https://global-mediator.freshdesk.com/support/solutions/folders/103000248234.
Other Improvements
- For the Monthly Pay Contract Type, instead of the GMJ Job Resource table, the Job Resource Price table is used when setting up the Job Task Resources for calculations.
- A new field Jira Assigned to was added to Jira Job Planning Lines to show the actual assignee in the Jira issue:
- Error handling enhancement when the Parent Issue Key on Task was changed in Jira. Now you can approve such an error to update the Parent Link in BC. The error message you will see is as follows:
Parent Link in Jira was changed. Approval will update Parent Link in BC
- Ability to post Job Journal Lines when the billable hours for the Task were changed and the logged time remained the same.
- Rounding up to five decimal places was implemented for the Original Estimate value.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article