Summary

The purpose of this article is to describe a way to write a script that will return the mapping of issue-key and user who resolved that issue:

Environment

Jira Server/Data Center on any version from 9.0.0.

Solution

The mapping "Issue Key/Jira user" can be obtained by using the expand=changelog parameter from the the REST API getIssue.

The example below shows a snippet of the information obtained when using this parameter:

<base-url>/rest/api/2/issue/<issue-key>?expand=changelog"

{
        "id": "10305",
        "author": {
          "self": "<base-url>/rest/api/2/user?username=testUser1",
          "name": "testUser1",
          "key": "JIRAUSER10100",
          "emailAddress": "testUser1@test.com",
          "avatarUrls": {
            "48x48": "https://www.gravatar.com/avatar/94fba03762323f286d7c3ca9e001c541?d=mm&s=48",
            "24x24": "https://www.gravatar.com/avatar/94fba03762323f286d7c3ca9e001c541?d=mm&s=24",
            "16x16": "https://www.gravatar.com/avatar/94fba03762323f286d7c3ca9e001c541?d=mm&s=16",
            "32x32": "https://www.gravatar.com/avatar/94fba03762323f286d7c3ca9e001c541?d=mm&s=32"
          },
          "displayName": "testUser1",
          "active": true,
          "timeZone": "Etc/UTC"
        },
        "created": "2024-09-12T09:21:41.323+0000",
        "items": [
          {
            "field": "resolution",
            "fieldtype": "jira",
            "from": null,
            "fromString": null,
            "to": "10000",
            "toString": "Done"
          },
          {
            "field": "status",
            "fieldtype": "jira",
            "from": "3",
            "fromString": "In Progress",
            "to": "10001",
            "toString": "Done"
          }
        ]
      }

 To get the name of the user who resolved the issue from the example above, you will need to:

• first look for the change made to the resolution field (in the Items → Field key)
• then look for the displayName key (which is testUser1 in the example above)

Suggested Script

• The script provided below will process multiple issues
• The variable issuekeys_csv in the script is having list of issue-key, comma separated

• To run this script jq utility should be installed in that host OS:

  #!/bin/bash
  # csv of Issue Keys
  issuekeys_csv="P1-1,P1-2,P1-3,P1-4"
  IFS=',' read -r -a issuekeys <<< "$issuekeys_csv"
  # Jira API base URL. Here replace <base-url> with Jira base-url.
  base_url="<base-url>/rest/api/2/issue"
  # Your Jira credentials (username and API token or password)
  username="user1"
  password="password1"
  # Iterate over each issue key in the array
  for issuekey in "${issuekeys[@]}"; do
      # Construct the URL for the current issue
      url="$base_url/$issuekey?expand=changelog"
      # Fetch the issue JSON using curl with basic authentication
      issue_json=$(curl -s -u "$username:$password" "$url")
      # Use jq to find the author of the change where resolution is set to "Done".
      user=$(echo "$issue_json"| jq -r '[.changelog.histories[] | select(.items[] | select(.field == "resolution" and .toString == "Done")) | .author.displayName] | join(" ")')
      # Output the result
      echo "$issuekey:$user"
      # Sleep for 300ms before the next request
      sleep 0.3
  done
  
  $ ./resolvedByUser.sh
  P1-1:testUser2
  P1-2:testUser1
  P1-3:testUser3
  P1-4:testUser4

• Please consider this just an example. It is not production ready, user would have to modify it as per requirement.