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,463,578
Community Members
 
Community Events
176
Community Groups

Why can't I select/see the Assignee field? while switching to new Experience it is there?

I am wondering why I cannot add a column for the Assignee, some posts make believe it is not possible, but recently have been using the New Experience and funny enough the Assignee is one of the main columns/fields in the roadmap, meaning the data is apparently present.

So why can it then not be selected in the Classic view or even used in the Team member creation?

1 answer

0 votes
Thomas Atlassian Team Jan 31, 2019

Hi @Nick De Groof,

 

The new Portfolio for Jira planning experience introduces core changes as described here, one of which is to rely on the Jira assignee field rather than the Portfolio Team Member field.

The Portfolio live plan experience is heavily relying on the Portfolio algorithm, which allows multiple people working on the same task, but the Jira Assignee field does not allow multiple values, hence the use of the Team Member field instead. To avoid confusion between those 2 fields it was decided to not display the assignee field along the Team Member field but to add some synchronization capabilities via the plan configuration option.

I hope that helps clarify some of the reasons behind the decisions made with Portfolio Live plan and since you mentioned it, let us know via the feedback option on how the new experience is working out for you!

 

Cheers,

Thomas

Hi Thomas,  thanks for the response, and while I can appreciate the logic, my point was that the data-field is available, as I can switch between the live plane and the new experience, granted each type of plan is based on either team-member or assignee, since in our case we have one issue(subtask), one assignee, this would enable to also see in the live plan who does what and would not force us to assemble redundant setup of teams in order to get some capacity planning from the live plan, could have been simplified.  Again understand design choices had to be made and this how it is.

BR, Nick

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events