Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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 Automatically change team base on the assigner?

Hi

Two team are working on one board issue. Is it possible to Automatically change team field in the issue base on the assigner?

Scenario:

eg :- 2 teams - Team A (developer), Team B (tester)

Developer (team A) develop the system and assign to the Team B member. It is not change team field in issue automatically. It need to done manually.
is there way to change this automatically? 

1 answer

1 accepted

2 votes
Answer accepted
Dave Atlassian Team May 01, 2021

Hi @janendra ranasinghe,

Unfortunately this is not possible using just Advanced Roadmaps however it might be possible to achieve this using the automation capabilities included along with Advanced Roadmaps in Jira Premium on Cloud.

When we were developing Advanced Roadmaps (back when it was known as Portfolio 3.0 on Server) we made the decision to not have "magic" behaviour relating to teams and sprints. For example we did consider restricting sprint assignment to the sprints associated with the team or automatically updating the team based on sprint assignment. We also considered doing something similar with teams and assignees. However the reason we opted against this was because it was not possible for us to enforce this within the issue details screen in Jira (and specifically with the case of assignee team there were potential edge cases like the assignee belonging to multiple teams).

Regards,

Dave

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

500 views 10 8
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