Our jira is set up by teams and not projects.

[Jason Chayer]

Our Jira is set up by teams and not projects. And I do not mean team managed. So, what this looks like is if we have a project, we have to create tasks in all the teams that will be working on this one project. This is somewhat difficult to manage, because tasks are scattered everywhere. I have found a solution to solve this, but it has to be done on every project being worked on.

Curious of opinions in the best way to overhaul this and have Jira set up by projects?

[Michel Neeser · Accepted solution]

Hi @Jason Chayer

If the tasks are somehow marked as being part of a project (e.g. with a label), I would just set up Jira by projects and bulk move the tasks into the respective projects. If you want to keep the team relationship, you could use the new team field.

[Jason Chayer]

@Michel Neeser - do you know if the new "team field" is only available in cloud? This seems like it would serve a useful purpose, as I have created a custom field for this.

Good call on the bulk transfer, I did not think about that. I do have a custom field that I created to help identify what tasks are related across the different teams.

Thanks.

[Michel Neeser]

@Jason ChayerAs far as I know, the team field is cloud-only. But you can of course just create a custom field for this.

And if you already have a custom field for your related tasks across teams, you should be able to bulk move the issues as I described above.

[Jason Chayer]

@Michel Neeser - thanks again for the feedback. I will probably just use my existing custom field for time being. We are going to have to move to cloud or data soon, maybe I will use that opportunity to restructure the setup.

[Michel Neeser]

@Jason ChayerUsing the opportunity of the move makes perfect sense to me.

Glad I could help! Please consider accepting the answer, maybe it is helpful for others as well - thank you!