Sprint Insights - the admins can see it but not the team members.
The feature is enabled for everyone, but sure why the admins can see it and the other team members cannot.
I would presume maybe there is another permission or setting on what data is required:
https://support.atlassian.com/jira-software-cloud/docs/manage-insights-in-a-company-managed-project/
Hello @Neil Wills
What exactly do you mean by the team members aren't able to see it? Do they not see the Insights button? Do they have the button but the panel comes up empty?
In what way has it been "enabled for everyone"? In the Permission Scheme(s) applicable to the project(s) encompassed by the sprint board, to whom is the View Aggregated Data permission granted?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for that information.
What is the Filter Query used by the board? That can be found by clicking on the ... button in the upper right above the board, then selecting Board Setting > General.
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.
I'm sorry, I was unclear with my request. I need to see the JQL of the filter, which is shown farther down on that screen.
I am trying to assess if the filter is selecting issues from explicitly named project(s).
Additionally, in what way has Insights been "enabled for everyone"? In the Permission Scheme(s) applicable to the project(s) encompassed by the sprint board, to whom is the View Aggregated Data permission granted?
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.
That does indicate the issues are coming from just one project.
In the permission scheme associated with that project, to whom is the View Aggregated Data permission granted? Example:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting feedback from different teams, some enabled it and other disabled it
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome!
When you have a moment, please consider marking the Answer as Accepted to help other users find posts with validated solutions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I will have to look at making groups as there are clients that will have access to jira, and these details while useful for the scrum team itself may be misleading for the stake holders, but that goes against transparency pillar of agile
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Neil Wills
Did you have additional questions on this topic?
If not and you feel that your question was adequately answered, please consider marking the Answer as Accepted to help other users find posts with validated solutions.
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.
This is now closed. We do have clients and will need to determine suitable groups and what data should be available to each group
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.