| Table of Contents |
|---|
Summary
When the reports states that a Custom Field cannot be set due to it not being the correct screen even when the Custom Field has been associate with all available Screens then this could mean that the JEMHC addon user does not have the correct Product access for that Project.
Error message:
Below is an example error message that will be shown.
| Code Block |
|---|
Issue couldn't be updated running as [accountId=xxxxx]. Retrying without user impersonation. Error: xxxxxxx.atlassian.net. Field 'customfield_xxxx' cannot be set. It is not on the appropriate screen, or unknown. |
Solution
The solution is to manually grant the JEMH application user access to the JSM/Software Product. However, since the application user is hidden from User Management page it means that you have to follow the steps below to access the JEMH application user profile to grant them access:
...