Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is it possible to assign task to the team not to the person?

We would like to assign a task to the Team. 

I already created a team.

3 answers

2 votes
Jack Community Leader Nov 18, 2020

In a word - No. There are a lot of posts in the Community and I recommend you use the search bar to seek these discussions out. 

Basically, Jira is designed to have single accountability for issues which doesn't work well when you assign a single issue to a team. Rather break the task into subtasks and assign to individuals. There are some posts on how you can do this for cases like Paired programming. Basically, you create a custom filed to define the team and either leave the Assignee unassigned or maybe assign to the 'lead'. There are other work-arounds you could consider too, e.g. use of Components, etc. With JSM you can create Team queues and filter the issues into those queues as well,

We did this using a custom field (which it sounds like you already have), a queue, and some rules. 

Here's the basic idea:

  • Custom drop-down field has the various teams
  • When that field is populated, an automation rule clears the assignee field and sends an email to the team.
  • The queue is configured to show non-closed issues with the team selected in the field. 
  • When a team member takes the issue, an automation rule clears the team value.

There's a little more to it, but that should be enough to get you going.

0 votes
Daniel Ebers Community Leader Nov 18, 2020

I would also advise against it - like Jack (and others, in different threads) already said. The approach from Paul is also very neat.
The quick and dirty solution (which should not be considered except for some very special corner cases) would be to create a user (named by the team) and assign it with a mailing list of the team.

The huge drawback I personally see for this scenario from real-life is that as soon as something like "Team_Accounting" or "DevPro" is listed in Assignee staff either claims:

"ah, well this is not me - let's see if somebody else takes it" OR

"DevPro - who should that be? I will not check further, more important things to do"

This is why this often kills productivity. I know that it is hard to convince requestors in this regard sometimes.

I also encourage you to read through what is said to that topic here in Community. The request has been raised some times.

Cheers,
Daniel

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

209 views 1 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you