Jira Insights includes items from different teams

[Giulio Campobassi]

Been using Jira insights and found it to be a great tool for in-sprint tracking. However, recently we've noticed that insights is picking up stories from other teams with a similar team name to our own. Our organisation's naming policy includes our team name in the sprint name. Another team also has a similar team name to ours. I think this could be affecting the filtering of the insights feature, and is subsequently including their tickets as well, skewing the data.

Observations

• We have noticed that the the other epics belong to a different team with a similar name to us.
• The other team has a completely different project prefix and code.
• Their tickets pollute the insights report making it unusable.
• Have searched the configuration features and cannot tune insights to strictly look at epics for out team only.
• Can't see a feature to control the filter through something more sophisticated like JQL.

So, is this a bug ? May be my access is limited and can't fix.

How can I make insights look exclusively at our project, such as JQL ? (Doesn't seem to be any option).

Searching configuration, and I only get these options to configure

Pressing the cog-wheel in the insights frame

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Projects, sprints, teams, and boards (with or without backlogs) are not intuitive to humans when they start to cross over.

Sprints are particularly confusing - a board/backlog will show all the sprints that an issue might be a part of (even when none are currently).

But, Epics are not project or team items.  An Epic is intended to group together stories from any of your projects.  They are not supposed to be team items, they are supposed to contain things from many different projects.

So you're seeing this because your Epics are trying to show you cross-project things. 

[Giulio Campobassi]

Thanks for replying.. but sorry, your answer does not address the question :

1. Is Insights be configurable ?
2. If so, does it support JQL or tools to confine insights to relevant work ?
3. Is it an access issue that my level of access can't see ?

I disagree "Sprints are particularly confusing". In Jira, your sprints will concisely see items for your project and be sortable/filterable by their respective epic if Jira administrators/scrum masters organise the filtering options in the configuration..

"But, Epics are not project or team items". I meant that items from other epics from different stories/bugs was appearing. I can see how the title was misleading, and have updated it and added some details to the question for clarity

Epics are used to meaningfully group work within your team, and in my case, whole swaths of bugs and stories relating to epics from different teams are appearing. The epics themselves doesn't appear to be the issue, I was merely describing how groups of stories/bugs was polluting the insights tool.

[Nic Brough -Adaptavist-]

1. Yes, Insights is configurable.
2. It does let you search for things via JQL, and it has reports that let you look at subsets of your data.

Sprints do seem to be confusing you here.  You say "In Jira, your sprints will concisely see items for your project and be sortable/filterable by their respective epic if Jira administrators/scrum masters organise the filtering options of the configuration..", which is completely wrong.   

A sprint contains items that could belong to many different projects, and many different epics.  An issue can only be in one Epic, and one project, but you can set it up so that an issue looks like it needs attention from more than one team (And Epics are mostly expected to need more than one team)

How are you using Epics?  Jira usually uses them to group together issues from many projects, where teams are not relevant, is that not how you see them?

[Giulio Campobassi]

So insights is configurable with JQL. 

And no, I'm not confused by sprints, nor how to arrange them. There's a lot of flexibility in the way to structure your boards. The problem for our insights board appears to be the default set up to filter Jira stories/tasks. Our Jira administrators are independent of our team, and will submit a request to them.

"How are you using Epics ?" you're making broad assumptions that are irrelevant to the insights question. So I'll just leave it there. TTFN

[Nic Brough -Adaptavist-]

Your question was about "Epics that belong to other people" and that "Issues pollute the Insight report". 

That is entirely relevant to the Insights question.  It looks like you do not understand what Epics are for, or where Insights data should appear when you choose to include it in your projects.