You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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 - 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.
@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.