Write JQL

[Sundram Trivedi]

How to find issues where the assignee is someone else, but the issue was merged by me.

[setti naga sudha chandrakanth]

Hi Sundram

Here is the answer for your question

you can try below one

assignee != currentUser() AND status CHANGED TO Done BY currentUser()

[Melbrin NGOUILOU]

Hi! I think there might be a slight misunderstanding in the JQL you're suggesting.

The query assignee != currentUser() AND status CHANGED TO Done BY currentUser() is valid, but it only finds issues where the current user transitioned the issue to Done, even though they were not the assignee. It does not tell you whether the user merged the related pull request — which is a different kind of action.

What the original question seems to ask is: How can I find issues that are assigned to someone else, but I was the one who merged the code (for example, the pull request)?

This is related to development activity, not Jira workflow transitions. Unfortunately, standard JQL doesn't allow filtering by who merged the PR unless you're using specific apps, APIs, or automation rules.

If Jira is integrated with Bitbucket, GitHub, or GitLab (via DVCS integration), you can view this info in the development panel on each issue, but it's not searchable via default JQL.

A common workaround is to use automation: create a rule that triggers when a PR is merged, checks who merged it, and adds a label like merged-by-me to the issue. Then you can filter with a simple JQL using that label.

Alternatively, you can use your Git hosting platform to find PRs you merged, then identify the linked Jira issues.

So in summary: the JQL you suggested works for workflow changes, but it doesn’t cover code merges — which was likely the actual intent of the question.

Hope this helps clarify things!

[Melbrin NGOUILOU]

Hi!

Unfortunately, standard JQL doesn't allow filtering by who merged the PR unless you're using specific apps, APIs, or automation rules.

If Jira is integrated with Bitbucket, GitHub, or GitLab (via DVCS integration), you can view this info in the development panel on each issue, but it's not searchable via default JQL.

A common workaround is to use automation: create a rule that triggers when a PR is merged, checks who merged it, and adds a label like merged-by-me to the issue. Then you can filter with a simple JQL using that label.

Alternatively, you can use your Git hosting platform to find PRs you merged, then identify the linked Jira issues.

So in summary: the JQL you suggested works for workflow changes, but it doesn’t cover code merges — which was likely the actual intent of the question.

Hope this helps clarify things!

[chad.leblanc]

ScriptRunner Enhanced Search may be able to assist in this, as it really extends the language you can use to search and filter for.  I use this for tracking changes from one sprint to another and by user - it could be just what you need.