We are using Behaviors to make several fields required on some issuetypes in one project. We you move a ticket from one issuetype to another these required fields are not enforced. For example, issuetype A does not have the some of custom fields that issuetype B has. Some of these additional custom fields are required on issuetype B. When the issue is moved from type A to type B, the wizard does not give the option to define these additional fields, regardless if they are required on issuetype B or not. How do I fix this?
oh, we used behaviors since we had trouble making a field required on one screen but not another within the same project. Users would get an error stating the field was required but it was not on the screen. We were trying to use the field configuration screen then to make a field required. Any suggestions?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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