Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


Is it possible to have context filters?

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
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 15, 2019

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
AUG Leaders

Atlassian Community Events