If the custom fields in Jira remain empty, even though everything has been described in the documentation and data is stored in MOCO, this can have several causes.
The following explains how to find out the cause of the problem.
MOCO configuration
The Jira plugin applies some filters when accessing the data. These are among others:
Only active clients are used. Not archived ones.
Only clients who have at least one active project are considered.
Only active projects are displayed.
Please log in to MOCO and make sure that all criteria are met.
Suppliers
Up to version 1.2.0, the plugin may not be able to deal with suppliers in MOCO. If you find the error:
java.lang.NullPointerException
at de.scolution.jira.components.MocoComponentImpl.lambda$getCustomers$0(MocoComponentImpl.java:138)
in the logs, please update to a newer version of the plugin.
API accesses and permissions
In order for the Jira plugin to retrieve all relevant data from MOCO, the user whose token is stored as the admin token needs authorization to access the projects' module.
To test this, we use a REST client and retrieve the clients from the MOCO API. In the example, the Chrome plugin "YARC" is used. However, any other Rest client can also be used.
The following data must be filled in:
URL | Here the Moco base URL is used and then supplemented with /api/v1/companies | |
|---|---|---|
Method | GET | |
Header | ||
Authorization | Token token=a1fcdf5671235cdefg78816409ec70045 | Here, the Authorization Header is set as follows: "Token token=<api token>". |
Accept | application/json |
As a result, 200 should appear and a list of deposited clients should be visible.
If this is not the case, please check your token and permissions in MOCO.
Firewall settings
Check the firewall settings in your company. The Jira server must be able to reach MOCO. To test this, run the following command on your JIRA server:
curl -X GET \
'https://{domain}.mocoapp.com/api/v1/companies' \
-H 'Authorization: Token token={api-key}'
|
Or alternatively, in a Windows environment: Call up your MOCO environment in the browser.
If this is not possible, make sure that the Jira server port 443 / HTTPS has access to the internet or the MOCO server.
Check logs
If all the solutions described above do not work, the log level for the MOCO plugin must be increased.
To do this, logging for the package “de.scolution” must be activated in Jira under System → Logging & Profiling. To do this, click on "Configure logging level for another package" and add the package "de.scolution" and the logging level "Debug".
With this information, you will be able to create a support ticket in our Service Desk Portal.
This may cause customer data (list of customers / projects / activities) from MOCO to be written to your logs. Please check the logs before passing them on to third parties or us.
