Use case: Adding issue key to work logs

Here is an example of an Automation for adding the issue key with a hashtag to work logs synchronized to MOCO with advanced synchronization.

1. Trigger: Work was logged

2. If-else condition

3. If the comment in the work log already starts with a hashtag, nothing will happen. Only the comment of the work log is logged.

4. Else, a web request is executed that updates the work log (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-worklogs/#api-rest-api-3-issue-issueidorkey-worklog-id-put )

   1. URL: {{baseUrl}}/rest/api/3/issue/{{issue.key}}/worklog/{{worklog.id}}

   2. HTTP-Method: PUT

   3. Web request body: Custom data

   4. Custom data:

      {
        "comment": {
          "content": [
            {
              "content": [
                {
                  "text": "#{{issue.key}} {{worklog.comment}}",
                  "type": "text"
                }
              ],
              "type": "paragraph"
            }
          ],
          "type": "doc",
          "version": 1
        }
      }

   5. Header

      • Key: Authorization

      • Value: Basic ******* (A Basic Authorization Token, preferably of an admin user, must be created here: https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/

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.