Looks like there is a huge disparity between Jira 5 and Jira 6 database schemas.
When I run the below statement on Jira 5.2.11, I get the desired results, no null values in pkey column. However when I run the same query on a clone instance running Jira 6.3.6, the values in this column are null. Where the table relationships get switched around? What do I have to do to have the same behavior or results in jira 5.
I don't really understand what the question is.
The structure of the data has changed because it needs to for whatever reason. I understand that this has broken a query you are running, but I do not see why it's a problem, because you don't explain what you are trying to get out of the query. "What do I have to do to have the same behaviour" can only be answered by "understand the data properly and adjust your query"
Backk at 6.1 time, the pkey column was made obsolete. It was replaced by issuenum
Depending on what you need, you can join jiraissue.PROJECT field with the PROJECT_KEY.PROJECT_ID to get the PROJECT_KEY field. You can concatenate the PROJECT_KEY and issuenum to recreate the pkey field.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs