Not sure I can elaborate beyond what you've already done! If the projects are all using the same "issue type screen scheme" and "field configuration screen", then they're all going to be seeing the same thing. However, there are a couple of less obvious things to check - assuming you have the two I mention above the same, have a look at exactly what fields are different (bear in mind that you need to check by issue type - a bug can behave differently to a feature, if you've configured it that way) I say this because although the screens might be the same, they can be further modified by "field context" (i.e. field "steps to reproduce" might only exist for bugs in project xyz, so despite the same schemes being in use in project abc, it won't appear there). Secondly, there are a couple of fields that vary based on permissions - a user who has the right to "assign issues" in project xyz, but not abc will not be offered the assignee field in abc. In other words, it's probably time to look at the specific differences between projects on a field by field basis. Unless, of course, I have completely misunderstood, and you're getting radically different layouts between projects? Not just some missing/extra fields?
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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