Jira Scrum Template Project - Custom fields not showing on issue/task/bug

[Deleted user]

We are trying to load user stories into a jira scrum template, I had original configure the issue from the project however when loading from a csv was not populating custom fields, only standard fields.

Then I read somewhere you had to create custom fields from jira settings, I have created them and assigned to all screens. Note, I don't see a scrum default screen, not sure if this is something that the system should create?
I can see a default screen and that is what I associated to my fields.
However, when I go into my project I only see defaults fields and cannot load any custom field.

[Angélica Luz]

Hello Alessia,

Welcome to Atlassian Community!

Just for a better understanding of the issue, I would like to know if you are importing the tickets to a classic or a next-gen project.

If it's a next-gen, there are many fields that are currently not supported, that's why it might not appear after you import the CSV.

• Available custom fields for next-gen projects

If it's a classic project, you must check if the fields have a value, otherwise, it might be hidden. Please, use the option "Where is my field" if you are using the old view. If it's the new view, it will show on the right side of the ticket.

Regards,
Angélica

[Deleted user]

Thanks , the problem was the template. I should have selected classic!
Thanks!

[Jan Rose]

It's 2022 now and Team-Managed projects still can't use many custom field types (such as Version-Picker)? Any plans on changing this? Especially the missing custom version picker field seems strange to me because there is one default version picker field available (Fix version).

Any plans of at least clarifying your documentation?
I wasted a lot of time configuring custom fields as stated in the documentation, then failed to apply them to my existing project which was set up with the SCRUM template.

Maybe adapting the screen listing the differences between team-managed and company managed projects would be a good start? Mention that you'll have different types of custom fields available and maybe link to the doc listing the available types!