Since we migrate to Jira 6.1, the field pkey in jiraissue table was set to NULL.
I need to generate KPI and pkey is used ... I need to adapt some sql statements but did'nt found where pkey is now store :-(
Tks for help,
To make the operation work fast we had to change JIRA internal storage, from now on jiraissue table store issue keys divided into project and issuenum. You must no longer use pkey and we null it in one of the upgrade tasks. There's also a new table storing all historical keys for a project. Read details in Preparing for JIRA 6.1.
I hope it helps.
This is not elegant, but you'd want to do something like this (mysql example):
select concat(b.pkey, '-', a.issuenum) as PKEY from jiraissue a, project b where a.PROJECT = b.id and b.pkey = 'FOO'
The numeric value that used to be part of jiraissue.pkey is now stored in jiraissue.issuenum. The alpha part of the old pkey can be found in project.pkey for the issue's related project.
The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events