...
With this Automation, every time work is logged, the issue key with a hashtag is added to the comment at the beginning if it does not already start with a hashtag.
| Hinweis |
|---|
If duplicate time logs are transferred to MOCO, it may be because the work log created in Jira has not yet been registered for MOCO when the trigger is executed in the automation. Technically, this means that the work log property has not yet been set by the plugin and therefore a new time log is sent to MOCO during the update. The solution is to wait until this worklog property has been set by the plugin. There is currently a ticket at Atlassian for the support of delays in the execution of automation rules (AUTO-238). Until this is implemented, the "Re-fetch issue data" action can be inserted several times after the trigger as an alternative:  |