The JQL query methods do not seem to support this particular query that I need, after my company renamed all my JIRA tasks (causing my separate change management system to be out of sync with the JIRA issues):
select oldstring, newstring from changeitem where oldstring like ‘IBMI%’ and newstring like ‘OC%’
Hello @George Loose
Welcome to the Atlassian community.
Your post tags indicate you are using the Jira Cloud product; the software-as-a-service product hosted by Atlassian. Is that accurate?
If so, you will not have any direct access to the backend database to run SQL queries.
In exactly what way did your company "rename" your tasks? Did they change the Summary field of each task? Did they change the Project Key so that the issue keys changed from IBMI-123 to OC-123? Did the issues get moved from the IBMI project to the OC project?
Hello @George Loose
Jira does not have a native feature to filter for issues that have been moved from one project to another.
There are third party apps that can provide that functionality. I have not used any of them so I can't offer a specific endorsement of any of them.
I found one mentioned in this post in an answer from the app vendor.
This post has an answer that suggests using the REST API.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks again, Trudy, for the good detail. I agree that the third party app you suggested looks like it would be helpful. However, since we have a large number of Jira users, it's not worth subscribing to a third party app for just my one task. I'm glad I can at least get the critical data I need by performing a one-by-one Search using my old issue Key to discover what is the new issue Key.
I really appreciate your prompt responses today! You have helped me keep on track with my project, now that I have a clear definition of how to get over this conversion hump. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Trudy,
Thanks for your helpful reply.
Here is an example of the History entry for all my tasks that got changed:
z updated the Key February 21, 2025 at 4:27 PM
IBMI-888 -> OC-1864
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My goal is to assemble a table of all these correlations, hoping to avoid a manual process of using Search one by one with my original IBMI task Key so that JIRA will show me the task with its new Key value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Additional reply to Trudy: Yes, the issues got moved from an IBMI Project to an OC Project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.