Hey Adam, I'm struggling to understand what you mean by "This panel will only show on issues where the user has specifically added the panel. The panel can also be disabled by the user." - do you mean the app button on the issue view?

What we have also discovered: I asked to one of my colleague to test the following: hide the panel, refresh the same page - panels stays hidden; then we navigated to a different ticket and panels were open. And the users who reported the issue told me they didn't turned these panels on, they were appearing by default. And that's the reason why I contacted you to see if we can restrict because the panels are visible without turning them on (might be also an Atlassian issue as well?).

Csaba - what kind of loading time are you seeing? This panel will only show on issues where the user has specifically added the panel. The panel can also be disabled by the user.

Just want to be sure I understand why an admin should block a user from being able to use a feature since the user chose to add the feature and can disable the feature themselves.

Hi Adam,

IMHO, the best would be if the admins would have an option to enable/disable on global level the panels /project. And after that, on the enabled projects the user can turn it on/off.

Let me know if you have any further question.

Regards,

Csaba

Csaba -

Got it. That's helpful.

Another question - right now each user must enable the panel before they see it loading on the issue. I believe it is per user per project.

Are you asking that a user shouldn't be able to enable the Team Insights panel at all on a project? Or is it sufficient to allow users to choose? (if you're looking for the "heavy handed" approach - could you share what you're hoping to realize?

Cheers,

Adam

Hi Csaba - just checking - by "Team Insight panel" do you mean: