1 answer
There's a few reasons why this is happening. First of all, it's important to look at the type of project you are creating the field in.
If your project is company managed, then you need to not only create the field, but also add it to the screens used in your project. In the most complex scenario, that may be on 3 different screens (one you use for creating an issue, the other ones for viewing / editing an issue). If you want the fields to be always visible to your users, then you also need to make sure they are in the context fields section on the issue layout in your project(s) as well, above the hide when empty line. If all these things are in place, it is even possible that they are not visible to users because of their personal preferences. And so, they too might have to enable the field on the create screen by clicking ... and then either selecting show fields or find your field:
In team managed projects, you don't need to worry about the screens I mentioned before. You are creating your fields directly on the issue layout there. The last steps I called out are applicable here as well.
On a final note: creating a field and adding it to the screens of one issue type (e.g. a story) does not automatically add that field to the screens of other issue types (e.g. a task). It might happen that you need to do the same configuration changes for other issue types as well - in both company and team managed projects. For that reason, always check with your other users what it is exactly that they are trying to do.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.