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

Is it possible to have context filters?

ie
If selection in field A = XXXX, then Field B shows drop list or checklist 1

If selection in field A = YYYYY, then Field B shows drop list or checklist 2

If selection in field A = ZZZZZ, then Field B shows drop list or checklist 3

 

Currently can have Field A and B, but B would need to contain all the list entries from 1, 2 and 3 - therefore miss matches are possible

Rough Example:

Field A (Device) : Mobile/Tablet/Desktop

Field B (Browser)

If Mobile: IOS/Android

If Tablet : IOS/Android

If Desktop: Firefox/Chrome/IE/Edge/Safari

1 answer

0 votes

Hello @Mark Cunningham

Thank you for reaching out.

Per your description and tag added to this question, I believe you're trying to implement a field dependency where field B will display a set of possible values depending of the choice in field A dropdown in a Next-gen project. Is that correct?

Unfortunately, this functionality is not possible yet for Next-gen since it cannot be added with cascading custom fields. There's a feature request opened to implement this functionality for Next-gen:

Remaining custom fields for Next-gen projects 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

For now, a possible workaround would be to migrate your issues to a Classic project by following the steps in the documentation below, where you will be able to add cascading fields to your issue view:

Migrate between next-gen and classic projects 

Let me know if you have any questions.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events