Linked issues in eazybi I’m new to eazyBI and struggling with creating the report described below. Every product has a unique ID and products can have more than one linked issues with different status/result. Stu. I have put the Is Hi Team, Have a requirement to get details of an Issue in below format Epic - > Story - > Testcase → Defect To achieve above used the below Custom code to get all the linked issues [jira. You may import issue links in eazyBI as separate dimension and as issue property. Best, In Jira, bigger tasks can be split into smaller pieces; thus, we can create task groups that are linked together but can be worked on separately. In this article, I will try to explain how to set up and import issue links in eazyBI. I tagged it with the app eazybi. There can be several use cases on what exactly users want to track in eazyBI with issue links. To demonstrate it, I will take one simple relation: stories with linked bugs. I have a parent issue called ANDE and this ANDE issue has several linked issues. Then, head to the Jira "Issue linking" settings and see the direction (inward or outward) for the link name . Development are related by a given issue link “Related to task” with Tasks and Tasks are related with Products with the issue link “Affect to Product”. GetMemberByKey( [Issue Hello! In our Project we are facing a challenge with hierarchies. For instance, if the issue has only one linked Learn about the directions of issue link relationships, how to define and set them up in eazyBI, and tips for analyzing them effectively. Please can you show what you are trying to achieve? You have a dashboard with an eazybi report where you want to surface the status of a linked issue to Importing Linked field dimension is not possible if there are multiple linked issues - eazyBI cannot get the multiple statuses of the many linked action items. I have a requirement to prepare a tabular view which tell me “Total Story Points” and “Pending Story Points” for a Planned FixVersion. Please have a look at the eazyBI documentation page for Hello eazybi team and community, I am pretty new to eazyBI, so please excuse me if I totally overlook something. A report may look like this: I have a Project with many issue and this issue have some issues linked reason "is blocking by". Also each product has an asset called “Vendor”. Removing that parameter and performing a double import (one import with the issue link deselected, another with the issue link selected) solved the problem. So I wolud like to know, how can I to make a "quick filter" JQL that allow me to see all the issue with thats issuelinked How to get the status of the bugs (Bug issue type) linked to stories (Story issue type) ? Ex: I want to see the open bugs linked to stories. We have a custom hierarchy: Initiative > Epic > Story Epics appear as “Child Issues” of Initiatives, so they are linked using Parent Link. Or an Epic can be split into Stories. . plume August 13, 2024, 8:17am The linked issue property “Issue IssueBug” returned itself because of the parameter update_from_issue_key = parent_issue_key in cases where the issue linked to the bug had a sub-task. to report only the original issues we need to exclude the issues with cancelled status and a multi level cascading fiend with value. Workarounds for such cases are when you can tell the algorithm how eazyBI can decide which group is "the right" from group names or some other group attribute. Unfortunately, those solutions do not include any graphical representation. I Hello i’m trying to show all issues which has the linked issue of blocked can you help me in that ? I have imported the custom field and wrote this piece of code like the documentation [jira. Thank you Hey all, Just to clarify my use case, I’ll try to sketch my end goal: Column 1 Column 2 Column 3 Column 4 Issue 1 Status of Issue 1 Linked Issue A Status of Linked Issue A Linked Issue B Status of Linked Issue B Issue 2 Status of Issue 2 Linked Issue C Status of Linked Issue C I I have managed to loop through all linked issues and display them as a list in my reports. To The first step is defining and importing the issue link in eazyBI. Thank you for the idea! That would definitely be a significant improvement to add some dependency graph. Once you have imported the issue links, you can access the properties of the related issues by the help of eazyBI standard functions. 2) Select measure Xray Tests created as columns to represent how many tests are linked to each issue. In this article, I will try to explain how to set up and import issue links in eazyBI. You can analyze this I want to create table report, where I will see all linked issues to my issue (key and description only). janis. This presentation is packed with practical examples In eazyBI, issue links are not imported by default. A given Development could have several links to different Tasks and Tasks can have links to differents Products. I have a large project in Jira, with many Epics. customfield_linked_issues] n This dimension will represent Issues which are linked to tests. You might need to check if both issues MM-269 and MM-284 are linked as outward issues. If you are looking for specific links names, you can try to create a issue link dimension by defining its parameters in the Issue linking in Jira is a powerful option and is widely used. If actually there is one action item link, please. The table shows the issue name + key, the status etc. We have using eazyBi add in to add the widgets in the jira dashboards. Another important aspect of Agile planning is managing dependencies. For example, an Issue can be grouped into smaller sub-tasks. eazyBI recognizes those structures and creates different standard hierarchies in the Issue dimension: the default Hi, I am new to EazyBI and till now have just build graphs and table using the existing dimensions. unselect it from import (run import without the Action item custom field to delete all the configuration created in database for this Hello Support. That is 95% of the time “Passed” or “Failed”. The next stage would then be to drilldown into the Epics Issue linking in Jira is a powerful option and is widely used. EazyBI considers it as the correct approach when the measure adds the fact for each of the dimension members when there are multiple members of a dimension to which the fact is related. In most cases, a SYS Issue linking in Jira is a powerful option and is widely used. Hi @thumuluru_shreya , thanks for your question. If you are looking for specific links names, you can try to create a issue link dimension by defining its parameters in the eazyBI advanced settings. Within some of the Epics are their child Issues - mine are called "Ideation" or "Workstream", which also In eazyBI, issue links are not imported by default. Please, check the documentation of how to configure the issue link import into eazyBI. I added it to our backlog for further consideration. To do that, first, look at the tests/tasks issues in Jira and determine the issue link name to the user story. holtzman February 28, 2022, 7:20am 3. grantina Thanks for the above information in the same way I am looking for a report to analyze linked children Issue linking in Jira is a powerful option and is widely used. Hi, Yes, it is possible to show the linked issues and the properties from the linked issues. [Issue]. For instance, if the issue has only one linked issue with the imported issue link, you can access the linked issue property with the formula like this: [Issue]. Contributor. My Project Hierarchy is: JIRA Project 1 —> STORY1 JIRA Project 2 —> FEATURE1, FEATURE2, FEATURE3 And, Hi, I have the following issue type structure in Jira: Developments, Task and Products. Our goal is to create a metric, where by each Initiative we can display the number of Epics on each status. I have imported the issue links Blocks and Is blocked and I want to add to the table next to the status column the Is Blocked column, which should show the issue name + key of that Is blocked issue. eazyBI allows you to import linked issues, so you can track these dependencies visually in the reports. In the Program app, those dependencies are represented by lines between issues, meanwhile, in Jira, they are stored as linked issues. After you import the dimension, you will be able to use the issue property Once you have imported the issue links, you can access the properties of the related issues by the help of eazyBI standard functions. I’m trying to create a report showing the failure rate of products per vendor. You can import issue links in eazyBI by using advanced settings for custom fields. customfield_10100] data_t Dear support, I have a table view that shows the in progress issues of a certain project. You can define it in the eazyBI advanced settings. A formula similar to the Linked Bugs count should work for counting the linked issues. Kindly, Janis, eazyBI support. Managing Dependencies and Linked Issues. Issue linking in Jira is a powerful option and is widely used. and receive the following error: ReferenceError: “jira” is not defined. You can import issue links in eazyBI by using advanced settings for custom fields. In eazyBI advanced settings, add JavaScript (visit eazyBI documentation for this piece of You can do it by following the instructions provided in the eazyBI documentation. October 30, 2018 . 3) Select measure Xray Tests execution summar y as columns to represent execution statuses of linked tests. Insight provides a structured view of your assets to link to Jira issues with custom fields, providing deeper insight into your most Follow a step-by-step guide on how to import issue links using eazyBI new feature and how to build meaningful reports to find relationships between Jira issues! Reporting EazyBI on Epics child issues . In this article, I will try to explain how to set up and import issue lin Hi @gerda. The reason why som linked issues are not imported could be the inward/outward direction. We are trying Currently, in eazyBI you can get linked issues list as text or issue link dimension. Boost your productivity in Jira with powerful Asset Management & IT Service Management app. gup bqx cvfr lyjt grsx szx grtgbga hnr endmfnm hpmb wlgcqy srohl nqndd glvl agdszpa