You can't associate different screens to a same transition, but you can include all the fields you need for both projects in the same screen, and then use different Field Configuration Schemes for each project. After that you can hide the fields you don't need in each project using the 2 different Field Configuration Schemes.
As I have associate field configuration schemes with issue type. This screen and field will display when i select the issue to which i have associate but my question is what about other screen we associate to other transition of workflow how can i association field configuration scheme with that screen
Field Configuration Schemes are used to associate behaviors (basically require or hide field) to fields in certain issue types in certain projects. This schemes apply to all screens used by those issues: Create, View, Edit, and transition screens.
You can't apply the schemes to a subset of screens.
By default all the fields are shown and optional. You can use Field Configurations for implementing a different behavior into a set of fields (make them mandatory and/or hide them).
You use Field Configuration Schemes to associate Field Configurations with Project and Issue type.
You can't associate a Field Configuration to a certain screen. Field Configurations always apply to all the screens.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs