Dear Plugin maintainer,
While tailing the JIRA server logs, I found these error logs happening quite frequently (every couple of minutes):
Toggl short synchronizer [comerge.joggler.synchronizer.TogglSynchronizer] Ignoring jira user XXXXX: No user mapping defined for this user.
...repeated for a lot users.
Also, after these sync messages, couple of these log pairs appear:
2015-02-26 10:23:15,423 QuartzScheduler_Worker-0 ERROR ServiceRunner Toggl short synchronizer [comerge.joggler.synchronizer.TogglSynchronizer] Worklog must not be null. 2015-02-26 10:23:15,706 QuartzScheduler_Worker-0 ERROR ServiceRunner Toggl short synchronizer [comerge.joggler.synchronizer.TogglSynchronizer] You can not edit the issue as it is in a non-editable workflow state.
I think it might come from the fact that we cannot modify Closed issues (but we don't want to allow that in our system).
Is there anything misconfigured in our system?
Any help appreciated!
The first log entries are just warnings, that you have JIRA users that are not mapped to toggl users. You can ignore this message or map all your JIRA users to toggl users. You can also turn this off on the JIRA logging configuration page.
I guess the the second error is caused by Joggler trying to change/update/add a worklog item to an already closed issue. If your workflow prevents this updates Joggler can't update it, hence the error.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs