我如何使用的一个版本API来获取项目和Sprint燃尽图? [英] How do I use the version one api to get project and sprint burndown charts?

查看:262
本文介绍了我如何使用的一个版本API来获取项目和Sprint燃尽图?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图使用的一个版本 API来获取项目和Sprint燃尽图。

我读<一个href=\"https://community.versionone.com/Developers/Developer-Library/Documentation/API/Data_API_Guide\"相对=nofollow>此页面,但我只是越来越糊涂。

有没有人做过类似的东西,对如何打API的任何提示,让我想要什么?


解决方案

在VersionOne的API不提供图片或图表的具体数据。您可以使用查询语言,其余端点产生是需要一个燃尽的数据。您需要能够读取/解析数据,并产生一个图自己。

有了这样说,一个燃尽图进行比较多少封闭估计与多少开放的估计和图形,随着时间的推移。所以,你需要知道三个数据:开估计,封闭的估计​​,和时间。您也想将其限制在一定的项目(和它会儿童)。

这应该让你接近你需要一个项目燃尽的数据:

<$p$p><$c$c>http://<host>/VersionOne/rest-1.v1/Data/Timebox?where=Schedule.ScheduledScopes='Scope:1055'&sel=Name,BeginDate,EndDate,Workitems:Story[AssetState!='Closed'].Estimate.@Sum,Workitems:Story[AssetState='Closed'].Estimate.@Sum&sort=+EndDate

请务必更改范围:1055到项目的oid,你有兴趣


这是我到了那里。首先,我在想好,你需要总结了一堆故事估计,所以我想我会做故事的历史查询:

<$p$p><$c$c>http://<host>/VersionOne.Web/rest-1.v1/Hist/Story?where=Scope.ParentMeAndUp='Scope:1055'

但很快就发现,你不能在你的根聚集。这也就意味着,如果我要总结的估计,我需要用别的东西像项目(范围),以获得数据:

<$p$p><$c$c>http://<host>/VersionOne.Web/rest-1.v1/Hist/Scope/1055?sel=Workitems:Story[AssetState!='Closed'].Estimate.@Sum,Workitems:Story[AssetState='Closed'].Estimate.@Sum,ChangeDate

该查询的问题是给你什么封闭与开放的估计看上去就像在不可思议的时间间隔;即只要项目改变。所以它不会使一个非常漂亮的图形。

但你也知道VersionOne的有关联到一个项目迭代和时间表的概念和故事都关联到迭代。所以我用,作为一个根查询和汇总的故事估计,且数据限制使用该时间表的项目。

所产生的数据是较规则(由迭代分组),包含正确汇总数据的估计。


那么还剩下什么?你必须汇总数据估计的聚集拿到总人数估计为您的项目。然后,你需要制作图(也许条形图或折线),其中每个数据点是在迭代结束。你会保持一个运行总计封闭的估计​​,并添加到迭代的总生产数据点。

I am trying to use the Version One api to get the project and sprint burndown charts.

I am reading this page but I am just getting confused.

Has anybody done something similar and have any tips for how to hit the api to get what I want?

解决方案

The VersionOne api does not serve images or chart specific data. You can use the query language and the rest endpoint to produce the data that is needed for a burndown. You would need to be able to read/parse the data and produce a graph yourself.

With that being said, a burndown graph compares how much closed estimate versus how much open estimate and graphs that over time. So you need to know three pieces of data: open estimate, closed estimate, and time. You'll also want to limit it to a certain project (and it'd children).

This should get you close to the data you need for a project burndown:

http://<host>/VersionOne/rest-1.v1/Data/Timebox?where=Schedule.ScheduledScopes='Scope:1055'&sel=Name,BeginDate,EndDate,Workitems:Story[AssetState!='Closed'].Estimate.@Sum,Workitems:Story[AssetState='Closed'].Estimate.@Sum&sort=+EndDate

Be sure to change Scope:1055 to the project oid that you're interested in.


This is how I got there. First I was thinking "well you need to sum up a bunch of story estimates" so I thought I'd do a historical query of stories:

http://<host>/VersionOne.Web/rest-1.v1/Hist/Story?where=Scope.ParentMeAndUp='Scope:1055'

But quickly found that you cannot aggregate on your root. What that means is if I want to sum up estimate, I need to use something else like Project (scope) to get at the data:

http://<host>/VersionOne.Web/rest-1.v1/Hist/Scope/1055?sel=Workitems:Story[AssetState!='Closed'].Estimate.@Sum,Workitems:Story[AssetState='Closed'].Estimate.@Sum,ChangeDate

The problem with this query is is gives you what the closed versus open estimate looked like at weird intervals; namely whenever the project changed. So it wouldn't make a very nice looking graph.

But as you know VersionOne has a concept of Iterations and Schedules that are associated to a project, and stories are associated to iterations. So I used that as a root to query for and aggregate story estimates, and limit the data to projects that use that schedule.

The data that is produced is more regular (grouped by iteration) and contains correctly aggregated estimate data.


So what is left? You'll have to aggregate the aggregation of estimate data to get a total estimate number for your project. Then you'll need to produce a graph (maybe bar or line) where each data point is at the end of an iteration. You'll keep a running total of closed estimate and add that to the iteration's total to produce the data point.

这篇关于我如何使用的一个版本API来获取项目和Sprint燃尽图?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆