On the GUI, when a link is removed it no longer shows on the screen when you are looking at the main screens.
We have looked over the linking table, but could not discern how to tell what the current linkage is vs the entire history. We only care about the current linking of the issue.
Hi @Brian Kimmel I'm not sure what you mean. When you care only about current links, why do you need to check linking table.
But if you are just concerned and need to know where the history items are stored, I can confirm it is stored in different tables so is you can't see link in DB table when it is removed, it should be ok.
Name of the table which stores history should be "changeitem".
When someone inadvertently links a story to the wrong epic and then fixes it, when you look through the GUI at the linkage, you will not see the linkage to the epic that was done in error.
My team creates reporting based on linkage, however the issuelink table and others seems to maintain history. So when querying, I wish to know how to only grab the current links like the GUI displays...it seems there should be some date related components that would allow for this.
Hi @Brian Kimmel still do not undestand, sorry ;)...
The only problem I can see is that
Is it the problem?
You just need to prepare report with current Jira data? If it is the case, it would be helpful if you share what type of Jira you uses (Cloud, Server/DataCenter). You can see some information in Issue filter or you can user Jira API (Java for server or REST API for Cloud)
We have reporting that we do out of the databases behind the GUI. The old/incorrect linkage still resides in the linkage tables even though the GUI does not display it. I wish to understand how the GUI knows what the current linkage is and what tables are being used to determine it so that our back end reporting is ONLY showing current valid links.
OK @Brian Kimmel I understand now. There is a table called issuelink which holds information about links between issues.
But it only stores active links (I just tested it). So it would be better to check your "reporting". Do you have more information about your reporting? What DB tables are used in it? Can you provide SQL query etc.?
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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