rally - バーンアップ チャートに LookbackAPI を使用するにはどうすればよいですか?

Question

LookbackAPI を使用してバーンアップ チャートのデータを取得する良い例が必要です。API に関する限定的な質問と回答がいくつか見られますが、それをどのように使用するかについての例はありません。ストーリー ポイントの現在の範囲とストーリー ポイントを完了する必要があります。

Answer 1

残念ながら、.NET、Java、および Python ツールキットは、ルックバック API をサポートするようにまだ更新されていません。その結果、Lookback API の REST エンドポイントに対して HTTP POST を直接実行する必要があります。ボディは上記の Mark W のようなもので、Content-Type は「application/json」です。

Chrome 拡張機能「XHR Poster」を使用して、ブラウザから送信する内容を試すことをお勧めします: https://chrome.google.com/webstore/detail/xhr-poster/akdbimilobjkfhgamdhneckaifceicen

Answer 2

Sorry for the scarcity of available examples. More and better examples will be coming as the LBAPI beta matures. I'd definitely recommend that you become familiar with the Lookback API (LBAPI) Documentation, as there are good examples there for formulating queries.

For a burnup, let's say you want to get the state Snapshots for an Iteration going from 15-Jan-2013 through 30-Jan-2013, and that the Iteration applies to a Project hierarchy that is four-deep. The following LBAPI query would obtain the PlanEstimate, ToDo, and Schedule State for Stories scheduled into that Iteration:

{
    find:
        {
           _TypeHierarchy:"HierarchicalRequirement",
           Children:null,
           _ValidFrom:{
              $gte:"2013-01-15TZ",
              $lt:"2013-01-30TZ"
           },
           Iteration:{
              $in:[
                 12345678910,
                 12345678911,
                 12345678912,
                 12345678913
              ]
           }
        },
        fields:[
           "PlanEstimate",
           "ToDo",
           "ScheduleState"
        ]
}

Where:

              $in:[
                 12345678910,
                 12345678911,
                 12345678912,
                 12345678913
              ]

Are the ObjectID's of the Iteration called "Iteration 1". It's probably easiest to get these Object ID's from a standard WSAPI query on Iterations: (Name = "Iteration 1"). For Iterations copied into a four-deep project hierarchy, we would see the four Iteration OID's similar to the above.

For charting, the toughest part right now is an easy way to deal with the Time-Series data. The most robust way to query and process LBAPI data currently is by working directly against the REST endpoint and processing the returned JSON results in your own code.

With Javascript apps, for processing the data and turning it into a Chart, the preferred toolkit is AppSDK2, specifically the SnapshotStore.

For Javascript apps, the Lumenize javascript library is separate from LBAPI, but was developed by Rally's director of analytics and is bundled in the SDK. You can find some examples of using LBAPI and Lumenize to produce charting as part of some Rally-internal and Rally-customer Hackathon projects here:

https://github.com/RallyHackathon

Please be cautious with these examples for a couple of reasons:

• Several aspects of the Lumenize namespace will be changing/renamed for clarity
• There's a bug in the current version of Lumenize where its timeSeriesCalculator does not correctly account for stories deleted or reparented.

Hopefully there will be an updated version of AppSDK2 bundled and released soon to consolidate the Lumenize namespace and resolve the bug, so that there's better glue between AppSDK2 and LBAPI for Javascript App development.