• s5_944047
    了解作者
  • 27.8KB
    文件大小
  • zip
    文件格式
  • 0
    收藏次数
  • VIP专享
    资源类型
  • 0
    下载次数
  • 2022-06-13 13:13
    上传日期
吉拉敏捷块 为什么要使用Looker Jira敏捷块? (1)快速实现价值-在几小时(而不是几周)内从您的Jira数据中获得洞察力。 Jira Block包括针对敏捷方法论的预建仪表板和内容,并围绕项目,版本,Spring和Issues进行了分析。 此外,此数据的组织方式掩盖了Jira的许多复杂性。 (2)集中的分析场所-进行自助服务报告不需要访问Jira。 另外,您可以将Jira数据与仓库中的其他数据(例如Bitbucket或Github提交)结合起来进行端到端分析。 (3)企业数据平台-项目经理和Scrum Master可以轻松构建自己的仪表板,并且任何用户都可以提问和回答自己的问题,保存和共享自己的报告。 此外,您可以利用Looker的高级计划功能在工作流中断时获取警报。 Jira数据结构和架构 Looker的Jira Agile块旨在与Fivetran Jira模式一起使用。
block-jira-new-master.zip
  • block-jira-new-master
  • issue_core.explore.lkml
    1.9KB
  • project_core.explore.lkml
    2.3KB
  • views
  • version_core.view.lkml
    1.6KB
  • epic_core.view.lkml
    837B
  • status_core.view.lkml
    875B
  • project_category_core.view.lkml
    551B
  • user_core.view.lkml
    1.2KB
  • status_category_core.view.lkml
    668B
  • sprint_core.view.lkml
    1.6KB
  • issue_type_core.view.lkml
    872B
  • issue_board_core.view.lkml
    816B
  • project_role_actor_core.view.lkml
    825B
  • user_group_core.view.lkml
    670B
  • resolution_core.view.lkml
    727B
  • board_core.view.lkml
    702B
  • field_option_core.view.lkml
    746B
  • component_core.view.lkml
    830B
  • worklog_core.view.lkml
    1.5KB
  • priority_core.view.lkml
    770B
  • project_core.view.lkml
    961B
  • sla_core.view.lkml
    1.8KB
  • project_role_core.view.lkml
    557B
  • comment_core.view.lkml
    1.2KB
  • issue_core.view.lkml
    2KB
  • project_board_core.view.lkml
    864B
  • marketplace.json
    911B
  • block_jira.model.lkml
    460B
  • epic_lookup.dashboard.lookml
    9.9KB
  • epic_core.explore.lkml
    1.4KB
  • resolved_issues_overview.dashboard.lookml
    11.9KB
  • manifest.lkml
    647B
  • LICENSE
    857B
  • README.md
    6.4KB
  • issues_overview.dashboard.lookml
    15.9KB
  • sprint_core.explore.lkml
    491B
内容介绍
# Jira Agile Block ### Why use the Looker Jira Agile Block? **(1) Rapid Time To Value** - gain insights from your Jira data in hours, not weeks. The Jira Block includes pre-built dashboards and content focusing on the Agile methodology, with analysis around Projects, Versions, Springs, and Issues. Additionally, this Data is organized to mask many of the complexities of Jira. **(2) Centralized Place for Analysis** - No Jira access required to do self-service reporting. Plus, you can combine your Jira data with other data in your warehouse (e.g. Bitbucket or Github commits) for end-to-end analysis. **(3) Enterprise Data Platform** - Project Managers and Scrum Masters can easily build their own dashboards, and any user is equipped to ask and answer their own questions, save and share their own reports. Additionally, you can take advantage of Looker's advanced scheduling functionality to get Alerts whenever workflows are disrupted. ### Jira Data Structure and Schema Looker’s Jira Agile Block is designed to work with the Fivetran Jira schema. Fivetran has abstracted away many of the complexities of the Jira data model to make it easier for reporting purposes. Because the Jira schema is very customizable and is different for every implementation, rather than attempting to replicate the exact structure of the Jira schema, Fivetran stores the data in more compact format, with Issues as the central focus. The Fivetran schema for Jira data can be found [here](https://www.fivetran.com/docs/applications/jira). Understanding the Fivetran implementation of the Jira data model is important for understanding the LookML model and how you will enhance it based on your own customized version of Jira. In a typical implementation, the majority of the customizations will be related to the `issue` table, so most of the following discussion will focus on the `issue` table. #### The `issue` table is comprised of three primary types of fields: * **1. A standard text field** - A standard text field appears on the Jira UI as a text box that you can type a value into. There are some more sophisticated ways of doing this in Jira, such as a Date Picker field, but the result is still a single value. When the data is stored in the database, the actual value that you entered is stored as a field in the `issue` table. * **2. A Single Value Select Field** - A Single Value Select Field allows you to choose one value from a pre-defined list of values. This may be from a dropdown list in the UI, or a set of radio buttons. When the data is stored in the database, rather than storing the value that you chose, a numeric id is stored in the `issue` table. The text value associated with this id is found in another table. In most cases, the id will be found in the table `field_option` which contains the id and associated value for most custom Select fields. There are some exceptions. If the Select field is referencing an entity that has its own dimension table, then the id would be found in the corresponding dimension table. For example, if you selected the `Issue Status` from a drop-down list, the id stored in the `issue` table would correspond to an id in the `status` table. * **3. A Multi Value Select Field** - A Multi Value Select Field allows you to choose one or more values from a pre-defined list of values. This may be from a dropdown list in the UI or a set of checkboxes. When the data is stored in the database, the id associated with the selection is stored in the database similar to how it is described in the Single Value Select Field. However, instead of being stored in the `issue` table, the id(s) will be stored in a standalone table that follows the naming convention `issue_[field_name]`. For example, if you had added a new Multi Value Select Field to the `issue` table called `Browsers Supported`, and provided a list of possible values that a user could choose from, the ids associated with those selections would be stored in a table named `issue_browsers_supported` along with the associated issue id, and the value associated with the browser supported id would be found in the `field_option` table. Every Multi Value Select Field associated with the issue will have its own standalone table. #### History tables * Fivetran also provides history tables that store the change history of each field in the issue table, including multi value select fields. Each field will have a separate history table associated with it which follows the naming convention `issue_[field_name]_history`. These tables store the issue id, the previous value of the field and the date of the change. * It is worth noting that Fivetran will not create a table until you insert data in the corresponding table in Jira. For example, until you modify the status of any issue at least once, your schema will not contain an `issue_status_history` table. For Jira installations that have been in use for a while, the only tables that won't be part of your initial Fivetran schema would be related to new custom fields that you add. For newer installations, it's possible that there will be new history tables added periodically as fields are updated for the first time, as well as new tables associated with new custom fields. These tables will need to be added manually to your LookML Model. ### Jira Block Structure The `issue` table is highly customizable. Administrators can add any additional fields necessary for capturing the data that makes tracking and reporting more effective. These additional fields can be either Single Select Fields or Multi-Select Fields. As the names imply, a Single Select Field can only contain one value, and a Multi-Select field can contain several values. Single Select issue fields are stored in the `issue` table. Multi-Select fields are stored in separate tables. For example, an issue may affect several customers, so it is represented by a multi-select field in the Jira UI, and stored in a separate table in the Fivetran Jira schema named `issue_customer_impacted`. ### What if I find an error? Suggestions for improvements? Great! Blocks were designed for continuous improvement through the help of the entire Looker community and we'd love your input. To report an error or improvement recommendation, please reach out to Looker support via email to support@looker.com or via chat to submit a request. Please be as detailed as possible in your explanation and we'll address it as quick as we can.
评论
    相关推荐
    • JIRA Cloud Kanban Combined WIP Extension-crx插件
      jira cloud Kanban组合WIP扩展名 使用此Jira加载项,您可以在敏捷过程中取得更多优势。 创建此加载项以实现真正的Kanban规则和方法。 此插件也有助于Scrum和Scramban方法。 一旦安装,它允许通常在通常的JIRA敏捷...
    • Scrum.Master-crx插件
      语言:English scrum.master工具有助于促进jira板上的scrums /每日立式 scrum.master通过创建随机流程和计时器,有助于促进jira板上的scrums /每日立场 团队成员。
    • JIRA Color Cards-crx插件
      语言:English 在JIRA scrum或看板上设置卡片颜色时,显着为jira卡片上色 在JIRA scrum或看板上设置卡片颜色时,显着为jira卡片上色
    • node_dashboard:显示 Scrum 团队从 JIRA 获取数据的速度和趋势的简单应用程序
      节点仪表板 显示 Scrum 团队从 JIRA 获取数据的速度和趋势的简单应用程序
    • scrum-notes-jee:从 jira 生成可打印的 Scrum 笔记
      Scrum-notes-jee 从 jira YouTrack 项目生成可打印的 Scrum 笔记: ://scrumnotes.myjetbrains.com/youtrack/ 要生成 jar,请运行 mvn clean install
    • jira-scrum-poker:吉拉的Scrum扑克
      吉拉的Scrum扑克 Scrum Poker for Jira使您的敏捷团队可以使用干净且交互式的用户界面,将其无缝集成到Jira软件中,从而共同评估其工作项目。 请访问上的官方文档,以了解有关JiraScrum Poker及其。
    • JIRA Total Board-crx插件
      语言:English JIRA Total Bord(作者Amit Shvil) 添加您的jira scrum的总故事点1.bord上的合计2.每列的合计
    • Efficient Jira-crx插件
      语言:English (United States) 查看吉拉时的好帮手 使scrum板更易于阅读
    • jira-scrum-poker
      该插件为 JIRA 提供了一个 Scrum 扑克解决方案,它与用于计算冲刺速度的 JIRA Agile 估计自定义字段很好地集成在一起。 入门 Atlassian 插件 SDK 提供了几个有用的命令: atlas-run将此插件安装到产品中并在本地...
    • Jira Scrum Points-crx插件
      语言:English 这是一个可以添加到浏览器的扩展,以显示我们的工程Scrum板上的总克拉姆点。 cj是一只狗。