I'm hoping someone can help! Insights will not populate reports for "Sprint Progress, Spring Burndown or Epic Progress" for the Active Sprint (using a SCRUM board). Any suggestions? I'm on a company-managed project.
Hello @Karina Jensen
Welcome to the community.
I haven't used Insights much. I just experimented with it and found that a couple of prerequisites.
1. There is a permission that has to be granted in your project's permission scheme, and your board filter has to specify a project. That is mentioned in this page.
https://support.atlassian.com/jira-software-cloud/docs/manage-insights-in-a-company-managed-project/
2. What ever you have chosen as your Estimation Statistic for your board, at least one issue in the sprint must be populated with that information.
3. If you have multiple active sprints you need to either select one of them to display in the board before or after you click the Insights button, or select one sprint within the Insights panel. It won't display information for multiple sprints at once.
@Trudy Claspill Thank you so much for your response! I really appreciate it. For some reason, we have 2 "Story Points" fields that have the same exact name of "Story Points" in the configuration but show up as 2 different fields below. If we use the "Story Points Estimate" field, Insights does not work but it populates on the card/ticket. If we use the "Story Point" field, the points do not populate on the cards/tickets and Insights sort of work :(.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are several things to unpack there.
Can you show us the configuration screen you are referencing that shows two Story Points fields?
Jira has an out of the box custom field named Story Points that is typically used for story points in Company Managed projects. It is bad practice to create another Custom Field with the same name as an existing one, though Jira does not prevent it.
In Team Managed Scrum projects you'll find a built-in custom field named Story Point Estimate. You won't see that field in the Custom Fields list where fields are created for Company Managed projects.
The two types of projects use two different "built-in" fields for Story Points.
What is the Estimation Statistic for the board?
What do you mean by "does not populate" on the cards/tickets? Can you show a screen image of that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill We aren't using any Estimation fields and I think that is why Insights isn't populating. I'm going to try populating that field when we start our next Sprint and see if that works. I'll report back if it doesn't. Thanks for your feedback!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Insights will need to have the Estimation Statistic option set in your board configuration.
And that is the field within the issues you will need to populate in order for Insights to show you data.
Below is an example from a board for a Company Managed project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, maybe what I found out will help. Our instance of Jira Cloud had a filter pointing to multiple projects/boards. Some of those projects/boards were archived. Once I removed those, everything worked as it should. Extremely useful feature, but none of the other basic help steps worked for us. After six months we finally figured out it was because of archived boards.
Check your's:
Go to board settings (my view of Jira has three dots in the right hand corner when looking at an active Scrum Sprint or the backlog) > General > Filter > Edit Filter Query
Remove any archived project(s). Save. Try the Insights button again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.