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,559,514
Community Members
 
Community Events
184
Community Groups

in the Roadmap, group by team, features are showing in both the team and no team swimlane

On the roadmap view when grouping by team, some features are showing in both swimlanes for the team & no team and some are only showing in no team.  All features have stories and assigned to the target QPI.   Looking for thoughts on why these items are not showing in the team swimlane

1 answer

0 votes
Neil Sproul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 15, 2022

Hi Suzanne,
Can you confirm all of the stories associated to the feature have a team selected on the story detail screen?  The behavior you described can occur when some stories have a team selected and some do not.  The feature will show in both the No Team and in its respective team grouping on the roadmap.

that makes sense and in some cases that was true and I set the team field.   There were some features where the team was set (by default when the item was synced from creation in JIRA to JA) but it was not recognizing it.  I had to manually click in the field and save it before it would actually recognize the value

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events