Avoid having Jira Owner activity in team Activity

[Maxime]

Hello everyone,

I'm facing a challenge in managing team activities on Jira and would greatly appreciate your insights.

As the founder of my company, I've created multiple teams (Creative Design, Software Engineering, etc.) and am a member of each, being their creator. However, I've noticed that whenever I open a ticket in any project, my activity becomes visible across all teams. For instance, when I open an issue in a Software Engineering project, this action appears in the "Team Activity" section of the Creative Design team's summary page.

I'm looking for ways to manage this cross-visibility of activities. Ideally, I want each team to see only relevant activities. What are the potential implications if I choose to leave all teams but continue to oversee everything? Will it affect project management or team coordination in any way?

Any guidance or experiences you can share on this would be immensely helpful.

Thank you in advance!

[Rob Smith]

I was hoping to see a good answer here. I have the same problem. I have created the "Teams" in Jira, and as a PM type I touch each Team when I create or change tickets, and it makes the Team Activity near useless because every team is flooded by my changes, instead of that feature displaying a stream of the Team's specific actions. If you have found any solutions, please let me know.

[Ste Wright]

Hi @Rob Smith 

The solution is in my other answer - don't be a part of every Team.

Is it necessary for you to be in the Team also? What benefit is it providing for you?

Ste

[Rob Smith]

I'm the PM across all the teams, trying to use it for organizational purposes of tickets that only impact a given team. The stream being flooded with tickets from other teams makes the feature less useful. I'm surprised that there is not some sort of delineation, because I create tickets for Team X, and they show up in the feed for Team Y, even though there is no assignment or cross over outside of my mere existence. It seems like any given Team is supposed to be managed by someone who _only_ works with that team. 

Is part of the point you are making that I as a PM could still go access Team X without being in it? That would declutter the stream which would be useful. I guess I had to think this through from another angle. Assuming that is your point. Thanks!

[Ste Wright]

Hi @Rob Smith 

Yes, you can still view the Team without being in the Team - and declutter their views in the process.

You could even create a Dashboard with multiple Filter Results gadgets, one per team, if you wanted a central view?

Ste

[Ste Wright]

Hi @Maxime 

This is a hard question to answer - as the impact will be based on what type of issues you're creating, and how your teams work.

For example...

• Are you working as part of all teams? If yes, are these issues not valuable to them?
• Are you creating issues on behalf of others? If yes, could you encourage them to take ownership of this?
• ...etc

Perhaps some more information about your involvement in each team and the type of issues you create would be beneficial here :)

Ste

[Maxime]

Hello @Ste Wright 

Thank you for showing interest in my question!

Yes! I'm working as part of all teams, building software along engineering team, giving tasks for the creative team.. and more!

So, every time I'm touching anything in Jira, my activity is shown in every single team "Team Activity", since I'm part of all of them, as the leader of all of them.

An example: creative team "Team Activity" is showing up me adding new tickets to Software Engineering projects.

[Ste Wright]

Hi @Maxime 

I'd consider whether you are part of every team - I'm not saying you're not, but there's a difference between...

• Working on issues as an engineer, and...
• Requesting work to be done by a creative team

But, I don't know the specifics of course - I'm just making assumptions to help guide what teams you should remain a part of.

If you remain part of all of them, the issue you're facing will continue to occur (which is also an option).

Ste