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?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event