Hi,  Jira issue link table is now available on Atlassian Analytics.  Please check out this announcement for details.  Closing this ticket. 
https://community.atlassian.com/t5/Atlassian-Analytics-articles/Jira-Work-log-and-Linked-issues-data-available-in-Atlassian/ba-p/2943659

Awesome!

Thank you dc89c36c9dff for your feedback, I'm glad that the workaround was helpful (until a proper fix/solution by Atlassian is ready).

Cheers,

Marwan

Hi Marwan, thank you very much for your help!

Your previous comment forced me to check our data structure and its constancy with Atlassian support. Apparently we had an issue with JiraIssueHistory. Support team ran "Re-bootstrap Job" and reloaded our site's data into the Atlassian Data Lake.

After these actions your workaround - https://www.marwansaab.com/how-to-enable-reporting-on-issue-links-workaround/ works like a charm.
Thank you once again for sharing it here.

Hope that it will help to everyone else who face similar limitations.

Best,

Ekaterina

Hi dc89c36c9dff,

I believe this comment "I'd like to reiterate my request and ask your team to prioritise a proper fix." is for Tina and Team (I don't work @ Atlassian)

Thank you for your feedback - not sure if you have a different schema / data representation compared to ours - I am very interested to understand the issue... we have this workaround working on all instances and connections.

If you like, please connect on LinkedIn (https://www.linkedin.com/in/marwansaab) and we can schedule a quick video call to help you troubleshoot the issue with the workaround.

Alternatively, you can try the below query to validate that your connection (data source) contains all issue links' historical entries:

SELECT `cte_IssueHistory`.`issue_id` AS `IssueID`
        ,`cte_IssueHistory`.`value` AS `LinkIssueKey`
        ,TRIM(REPLACE(REPLACE(`cte_IssueHistory`.`value_string`, 'This issue', ''), `cte_IssueHistory`.`value`, '')) AS `LinkType`
    FROM `jira_issue_history` AS `cte_IssueHistory`
    WHERE (`cte_IssueHistory`.`field` = 'Link') and (`cte_IssueHistory`.`value_string` is not NULL) 

Cheers,

Marwan

Hello Tina and Marwan, thank you for following up on my latest post. To answer your question, Tina, "will you also need some kind of issue hierarchy structure to make it more useful?" — that would have been nice. However, I believe in many cases it's quite standard for many projects to have the Epic → Story → Task hierarchy.

In my use case, though, we face an issue with problems related to issues linked from other projects or from the same project that are the "same type" in terms of hierarchy but are named differently (custom issue types).

___

Marwan, thank you for the instructions on the possible workaround.

However, in my case, this workaround doesn't seem to work.

I followed the steps described in the article (created a custom table, etc.), but it only showed me 3 issues from a Software Project (Key = INCI), which has existed for over 5 years. We have at least 1-2 issues linked in almost every ticket from the same project, so the Issue Key starts with the same INCI prefix.

To investigate further, I ran the exact query with a single filter on the "issue key" like (nothing else), and it returned only 6 issues in total over the entire period, which seems highly unlikely.

I'd like to reiterate my request and ask your team to prioritise a proper fix.

Thank you!

+1

Any ETA?

Hi dc89c36c9dff and all,

We have implemented a workaround (~1 year ago) and been using it for all kind of issue link reporting (in our case, we have one that only shows dependencies)- including aggregation based on hierarchy.

As mentioned before, this workaround comes with a minor limitation - however, this has not been an issue in all our use cases.

I have created a quick post explaining the workaround, including the full query of the custom table that you can use as is if you wish to do so.

How-To Enable Reporting on Issue Links (Workaround)

Please note that once Atlassian releases the official Issue Link data in AA schema - I will be updating this post to "replace" the custom table's SQL and leverage the out-of-the-box functionality - and that should automatically update all existing charts using this custom table.

Hope that helps.

Cheers,

Marwan

Hi dc89c36c9dff , thanks for the explanation of alternatives. This feature will be released soon.  There have been multiple technical barriers that we had encountered to enable both the join and coverage of LinkedIssue.

A question for you:  when Issue Link data is available, will you also need some kind of issue hierarchy structure to make it more useful?  

Thank you

Hi team, please prioritise this feature, as I believe there are ways to query this kind of information already in place for example in JQL (like linkedIssueType expression).

If I can query linked issues at least per its type in JQL and use such filters to build up reports in a standard Jira "Dashboards" not having this possibility in the more advanced tool like Analytics, and not being able to reproduce reports that already exist in "Dashboards" is a really big issue that has to be resolved asap. 
Having this request remain in progress for 9 months is quite "remarkable":

 
 made changes - 26/Mar/2024 5:39 PM

Boa tarde, temos alguma atualização desse Bug?