nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to get the committed points for the current sprint where the event type as sprint start

Satya Ramesh

Need to find the committed points (of the stories) at the time of sprint start. Not on the same date, because there could be stories added to the sprint later. But I need to find the points of all the issues when we hit Start Sprint. Checked many questions in the forum's but could not find the correct answer. Could someone from the community help?

I need to find this in PostGreSQL.

Accepted answers

All comments

Trudy P Claspill

Hello @Satya Ramesh

Welcome to the Atlassian community!

Trying to get the committed points for a sprint at a date after the sprint has started is extremely difficult with native functionality. The issues in the sprint may have had changes to their story point values, and issues may have been removed or added. You would have to sort through history to find out if the story points had been changed and if issues where added/removed.

In my opinion, the best way to get that information is to use Automation for Jira and create a rule triggered by Sprint Started. When that rule is triggered, add steps to retrieve the issues currently in the sprint, sum up the points, and record that information by sending it in an email or posting it to a Confluence page.

There may be third party applications that you could add to your Jira instance that could get the information for you. You can look on the Atlassian Marketplace for such apps.

Nic Brough -Adaptavist-

I can not give you a more appropriate answer to that, Trudi has it exactly right.

The reason I am commenting is that I am not sure that "committed points" is the right thing to look at. Without knowing your processes, I default to off-the-shelf Scrum, where "committed points" will mean "the sum of the SP we committed to doing in this sprint". Adding or removing issues from the list, or amending their estimates after starting the sprint simply means the scope has changed, and you will need to think about it in the retro.

Meghan LaClair

@Satya Ramesh

If you are open to 3rd party solutions this is something that we provide visibility into with minware. We provide plug and play software engineering metrics linked to ticketing, code sources and calendar data.

Our Sprint Insights summary provides a full view of how story points flow throughout a sprint.

Sprint Insights Summary.png

Disclaimer: Marketplace partner

Satya Ramesh

Hi all, thank you for your quick response in helping me out.

Actually the requirement is to fetch the data from PostgreSQL and prepare a report and send it to the concerned people. I do not have control over the Jira.

Is there anyway we can fetch all the committed points when the sprint started from PostgreSQL?

For example, when the sprint started if there were 20 issues assigned to the sprint, I need to fetch committed points only for those issues. Any issues added to the sprint later can be ignored.

Is there anyway to find it out in PostGreSQL?

Asam_atis4w

Is there any other way to find committed points for current sprint in PostgreSQL?

Nic Brough -Adaptavist-

Yes, but it is not the right way to do it, the best thing you can do is create a REST API call that simply calls "opensprints()"

If you try to do this in SQL, you're going to need to have to think about the current sprint, how the issues in it are identified within it, and how to read the story points from them. There's 6 joins in there and that's just minimum you need!

Satya Ramesh

Hi Nic, thanks for your response.

May I know the 6 tables that needs to be joined?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

postgres