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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,000
Community Members
 
Community Events
176
Community Groups

Team vs assignee

Edited

Hello

 

We would like to use the Advanced Roadmaps in our organization.  The problem is using Team – we are assigning issues to person.

We are considering the following solution – create team per person and create automation that copying value from assignee filed to the Team  field.

I tried to create this automation and it doesn't work. May be the problem is the different field type?

Anyway – may be someone can help me with automation or have another idea how to use it?

 

 

 

 

  We in data center configuration 

Thanks in advanced!

Sofya

1D987D13-0C47-45C5-90B5-94A93ADEF301.png

1 answer

1 vote

@Sofya -

Team field in AR for Jira is unique field type and should not be used as issue assignee.  Furthermore, Team should contains members of the team (i.e. issue assignee from your project) and not meant for having one assignee per team setup.

However, you can expose the field to your project's issue view screen.  If you want the ability to edit this field within the Jira issue screen (EDIT screen etc.) outside of your plan, then you will have to ensure the Team setup in your AR for Jira plan is set as "Shared Team" and cannot be private only to your plan.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Thank you very much Joseph!

I understand the methodology of working with team, but in our organisation we set estimation per assignee… so as solution we decided to create team per assignee. 

I’ve tried to create automation that can set Team from the assignee field then it edited… but the assignee field is not in the list of options… probably it’s not possible… maybe the type of assignee field does not much…

Is a type of field can be a problem?

 

thank in advance!

Sofya

@Sofya -

Team field (one used by AR for Jira) and Assignee field used by Jira Software/JSM are different data type and unique to itself.  Assignee field is user picker and Team is not.

This is why you will have issue with automation rule setup.  Even you setup the rule such as if assignee = a specific user, then set the Team to a specific value.  It will not be scalable because you have to hardcode the different assignee to different team combinations + very difficult to manage it.

Best, Joseph

Thank you very much!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events