This field has no purpose if it can not be used!

Dear all,

I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

Sincerely,
Aakrity Tibrewal
Jira DC

Is there any update on this feature request?

Silly how hard it is to try to get a Team concept set up in Jira! Only to find that it is not implemented as you would expect. 

Create an issue, assign it to a team, so that the team can work on it, report on issues it is responsible for in a sprint, velocity, etc.

When is this expected to be fixed/implemented?

This seems to be counter productive or half baked feature in production.

This nonsensical error is still there, if I got a QA team and I can't add it as a value on a bug issue what's the point of having it in the first place?

I think that this is meant for specific use in the 'Plan / Advanced Roadmap' module so that you can forecast needing 3 resources from a shared testing team for example. Mainly to be used in a forecasting / dependency mapping exercise for project planning.

But I agree there should be a product native OOB concept of teams / assignment groups for general service desk request and breakfix activity.

The approach of having defined named individuals for project tasks makes perfect sense when you have a limited number of people on your project team. When you are actually dealing with high volumes of requests / breakfix / alerts, assigning to individuals doesn't make sense any more, even if you use the auto-assignment. You assign to a team who will then pick up.

Same problem here... I've created my team but can't assign issues to it. What's the purpose of teams then?

Yeap, same issue. Is there any workaround to this that people have used here on their projects?

I was thinking perhaps switching form teams to individuals who lead the team, but I guess this is not always ideal.

I am also curious about this one, as the current situation makes the whole notion of Team pointless... or maybe I just didn't quite get it? We introduced a custom field to remedy this too, but it's not ideal.