New Fields Experience in Jira Team-managed Projects

[#1]

Hi everyone,

Carol from the Product team here, and I’m pleased to announce a new experience for managing fields in team-managed projects. We’ve heard your feedback that it can be hard to learn how to configure fields in Jira, and this is one of the first steps we are taking to bring you a better experience for managing fields.

Best of all, these changes come with performance benefits and helps you get your work done, faster.

✨ Introducing the new Fields page

🔍 What is it?

The fields page is the source-of-truth of what fields are configured to your project. Here, you can add existing fields, create new fields, and remove/delete fields you are no longer using.

Adding an existing custom field

Creating and editing a project field

Once you have updated this list, you will see the changes reflected when you select fields for filtering, including in the Issue navigator, List view, Calendar view, and JSM queues. Of course, adding it to the respective issue types will also allow you to update your field when creating or editing your issue!

We’ll begin progressively rolling this out over the coming weeks, in the meantime, please feel free to leave any questions/comments/feedback in this post.

📝 FAQ

Is this available in all Jira products?

• This will be available in all team-managed projects for Jira and Jira Service Management. A fields page already exists for Jira Product Discovery, and will continue to work as it does today.

A field I could previously see when I was filtering in the Issue Navigator is missing, is my project broken?

• We’ve implemented a change to only show you relevant fields - to see this field again, please add it to your project using the Fields page in Project Settings. Rest assured none of your data is lost.

Regards,

Carol

[__ Jimi Wikman]

I am not a huge fan of Team Managed projects, but this is really good!

Two thumbs up for this great addition!

[Carol Low]

@__ Jimi Wikman - thank you! we're always looking for feedback on how we can improve team-managed projects, so let us know if you are open for a chat, or send through your thoughts here (or to me directly clow@atlassian.com)

Hopefully it is good news that we will be bringing this to company-managed projects too? (with a company-managed twist of course)

[__ Jimi Wikman]

@Carol Lowadding this to company managed projects make this an even better announcement indeed :)

I would be happy to have a chat, but time is a bit short at the time, but once I have a bit more I might take you up on that offer :)

Keep up the awesome work!

[Phong Nguyen - Atlassian Solutions Engineer]

What a great improvement!

By the way, for anyone using the smart value to access global fields via automation ({{customfield_id}} or {{customfield_name}}), we nee to add those global fields to this team-managed project setting section unless the smart value will return an empty value.