I'm creating a template for projects from scratch, including workflows, issue type field schemes and issue type screen schemes, plus permissions and notifications. Everything's going pretty well except....I've created multiple field configuration schemes. Each is to be used for a different issue type (in some cases, multiple issue types). But when I configure the Screens for a field in a configuration, the new settings are carried over to ALL of the other field configurations, overwriting the unique settings needed for the other issue types. Has anyone seen this before? What's going wrong?
I'm a bit confused - your question is mostly about field configurations, but you start talking about screens in the middle. Screens and field configs are (effectively) totally separate things, and amending a screen has no effect on field configs at any time. Could you explain exactly what you are changing that seems to be causing the problem?
I also need clarity that Nic is requesting. Are you creating new fields for each field configuration scheme? If you are sharing the same field, then all field schemes with that field will be updated. Can you state which fields or field types you are trying to customize?
Hey, thanks for taking a look! I think the confusing wording was a sign that Friday afternoon had arrived. Maybe my issue is the same kinda thing.
Here's what I'm doing:
That's probably where the confusion came from. To continue:
Hope this bit of detail helps clear things up.
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