You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We want to create a field that acts the same way as issue type field and based on that type of ticket can populate in a dropdown.
For example, we support JIRA and Confuence Application
we want to create this field called "Type of Support": (Select list ) (JIRA and Confluence) options. Based on what the user selects the regular system "Issue Type" field comes up and user selects the issue type and the field on the form generates based on the type of issue type the user selects.
Hi @Spruha Shah
However, this is what projects are for. It looks like you have two projects here - one for Jira Support, the second for Confluence Support.
With two projects, you will be able to decide which issue types are available on each - and what fields, screens and workflows are applied to each issue type.
Also, an extra benefit is they'll be distinctive on boards or filters due to having unique project keys.
Is there a reason project is insufficient for this setup?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.