EasyAgile Programs - API to Access the Sprint/Iteraiton

[Bill Lakenan]

I'm having trouble with the EasyAgile API to get details an issue.  I'm following the API documentation and trying to retirve which sprint (or sprints) an issue is associated with.  All of our teams use Kanban, so we cannot use the "Sprint" attribute.  When I call 

/rest/api/2/issue/{issueKey}/properties/EAP-schedules

I get back a JSON block that includes "columnIndexes".  I was hoping that this would contain a list of columns where the issue appears on the Team Planning view.  For example, I expected that a story that spans sprints 1 and 2 would have "columnIndexes" as [0,1].   Instead, all issues only include the first columnIndex where they appear.  This does not help me as I need to know when the issue will be completed (aka the last sprint).  

Seems like it might be a bug, but hopefully I'm wrong.  Help?

[Jared Kells · Accepted solution]

Hi Bill,

I'm Jared one of the developers at Easy Agile on the Programs team.

You are correct that the `columnIndexes` property only stores the initial column that the ticket was scheduled in and not all the columns the issue is displayed in.

For Scrum boards in Programs things are straightforward, the issue will use the sprint field on the issue. There is an explicit action performed by the user to complete a sprint and choose whether to roll issues into the next sprint or to the backlog.

For Kanban support in Programs we simulate the behaviour of sprints but because there is no completion event we need to use a heuristic to determine what happens to an issue after a sprint period is complete.

We assume that incomplete issues on Kanban boards roll from the scheduled sprint into the following sprint until they're resolved.

We do this using the resolutionDate field on the issue. As we know the date range for each column we display the issue in every column between when it was scheduled and when it was resolved.

For example if an issue was scheduled in column 1 and it was resolved mid way through column 3 we should show the issue in columns 1, 2 and 3.

It might be possible to implement the same heuristic in your integration. You can determine the start date of the increment and the length of the sprints in weeks from the `Increment` object in the API. From those values  you can calculate the start and end date of each column.

Please accept my apologies. I know our internal data format is not ideal for reporting. We do have a ticket on our backlog to expose the column for Kanban boards in a more user friendly way.

Cheers,

Jared

[Bill Lakenan]

Jared,

Truly appreciate the informative response.  I understand the heuristic you described and can apply it in our integration.  It is very refreshing to get a direct response from a member of the development team for any product.  Kudos for the support.  Thanks.

- Bill

[Jared Kells]

Thanks Bill!