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

Labels not showing on backlog when field is named something other than label?

We are trying to utilize the next-gen project, we really like some features but others are still a little hard to navigate. We use the current sprint board view a lot but the filtering options are limited. We want to be able to filter by specific work focus (on the old jira board this was done by components and quick filters) but those options are no longer available. So, I created a a label field called "team" and added default labels to select but as it turns out this functionality doesn't seem to work on next-gen. As those labels don't seem to be recognized as labels if that field isn't named label (even though it is technically considered a label field). Any suggestions?

1 answer

1 accepted

0 votes
Answer accepted

Hello Eggy,

Thank you for reaching out to Community!

The option to filter by Label was recently released and this filter only recognizes information added in the system field, so if we created a field of the same type, it won’t be recognized for the filter, but any information added to the system “Label” field, will work.

With that said, I really understand that next-gen is very limited in features and this type of project was created for small teams, that’s why many features of classic projects were not added.

We have a feature request suggesting the implementation of quick filters on next-gen:

 Also, I want to share with you the main feature, that has the sub-tasks with everything that customers are asking for next-gen:

Please, click on vote and watch for all features that you believe it’s important for your environment.

Regards,
Angélica

Thanks Angélica,

Label field only really works for the system field. 

I realize that next-gen has limited features because it was created for small teams although labels I would assume is valuable for teams of any size especially since the ability to customize and create quick filters is not available. I will review the feature roadmap and vote for the ability to create quick filters. 

Like Angélica Luz likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events