Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Replicate Jira's Velocity Chart and Sprint Report metrics #102

Open
2 of 4 tasks
whitneywoodlr opened this issue May 25, 2023 · 1 comment
Open
2 of 4 tasks
Labels
status:scoping Currently being scoped type:enhancement New functionality or enhancement update_type:feature Primary focus is to add new functionality

Comments

@whitneywoodlr
Copy link

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

We need a snapshot of story points that were "committed" at the beginning of a sprint and story points that were "completed" at the time the sprint ended. Teams would like to track sprint velocity over time in one place (ex: Tableau dashboard). Jira's interface for the Velocity Chart is limited to the past 7 Sprints. Jira's Client API does not currently provide these metrics.

Describe alternatives you've considered

Jira's Front-End API (greenhopper) provides the data needed but is unsupported by Jira, and access could be disabled anytime.

Jira Front-End API endpoints:

Velocity Chart:

  • https://{site_name}.atlassian.net/rest/greenhopper/1.0/rapid/charts/velocity?rapidViewId={boardId}
  • Returned data: sprint_id, estimated_points, completed_points

Sprint Report:

  • https://{site_name}.atlassian.net/rest/greenhopper/1.0/rapid/charts/sprintreport?rapidViewId={boardId}&sprintId={sprintId}
  • Returned data (below includes my renaming of the returned data):
    'id': 'issue_id',
    'key': 'issue_key',
    'typeName': 'issue_type',
    'priorityName': 'issue_priority',
    'done': 'issue_is_done',
    'assigneeName': 'issue_assignee',
    'epic': 'issue_epic_name',
    'epicField.issueId': 'issue_epic_id',
    'currentEstimateStatistic.statFieldValue.value': 'issue_EOS_points',
    'estimateStatistic.statFieldValue.value': 'issue_BOS_points',
    'status.id': 'issue_status_id',
    'status.name': 'issue_status_name',
    'status.statusCategory.id': 'issue_status_cat_id',
    'issue_type': 'issue_status_type',
    'added': 'issue_added_after_BOS',
    'completedIssuesEstimateSum': 'sprint_issue_points_completed_EOS'

Are you interested in contributing this feature?

  • Yes.
  • Yes, but I will need assistance and will schedule time during your office hours for guidance.
  • No.

Anything else?

Jira's Velocity Chart definitions

@fivetran-joemarkiewicz
Copy link
Contributor

Hi @xrayattack thanks for opening this feature request to add Jira velocity and sprint reporting metrics to the Jira dbt package.

In the past we have avoided including reports like this within the dbt packages as they can be fairly opinionated and vary across each environment. As such, we have built the jira__daily_issue_field_history model which should have all the components available to build your own custom velocity and sprint reports.

That being said, we have attempted a similar report in the past with our Zendesk package and have seen success. To be honest, this report would take quite a deal of time and likely be a large scale update to ensure the report is usable by all our package users. I will continue to scope this out and see how feasible it is for us to include. I will be sure to add more updates here as we scope this out and consider folding it into a future release.

@fivetran-joemarkiewicz fivetran-joemarkiewicz added status:scoping Currently being scoped update_type:feature Primary focus is to add new functionality type:enhancement New functionality or enhancement labels May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:scoping Currently being scoped type:enhancement New functionality or enhancement update_type:feature Primary focus is to add new functionality
Projects
None yet
Development

No branches or pull requests

2 participants