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,556,162
Community Members
 
Community Events
184
Community Groups

can we create a field similar to issue type field ?

Edited

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. 

1 answer

1 vote
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 08, 2020 • edited

Hi @Spruha Shah 

Not natively.

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?

Ste

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events