nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I show custom field from a next-gen project on a classic board

Colin Hendricks_yn2e8d

I have a board in a classic project that shows a mix of stories from classic projects and next-gen projects. I would like to customize the card layout in this classic board to include a field from one of the next-gen projects, but I don't see my next-gen fields in the list of fields to choose from in the Card layout screen. Is there a way to add a next-gen project's custom field to a classic board card layout?

Accepted answers

Gabriele Franck

Hi, Colin

The Next-Gen is an individual project, designed to be more straightforward than the classic Scrum and/or Kanban template, with a single board, simple workflow and limited field options to be used at the issue detail view, this includes that issues from your Next-Gen project will only be available inside of that project, you shouldn'thave issues from your Next-Gen project being used in another Next-Gen project or a classic board.

So, answering your question, you won't be able to add a custom field from a next-gen project into a classic board template as these boards use different schemas for custom fields.

Let me know if this clarifies

Gabi

All comments

Gabriele Franck

Hi, Colin

So, answering your question, you won't be able to add a custom field from a next-gen project into a classic board template as these boards use different schemas for custom fields.

Let me know if this clarifies

Gabi

Colin Hendricks_yn2e8d

Yes, thanks. Understand.

Just FYI, stories from my next-gen project are showing up fine on my classic board (which lives in a classic project). I'm even able to map their statuses into my classic board columns, which is great. There's just this limitation about card field configuration, which I suppose is an understandable place to draw the line on supporting interaction between classic and next-gen.

I do think it's good to have interoperability like this between classic and next-gen projects to help us migrate over time between the two. Lots of your existing customers will have multiple scrum teams that will probably want to mix classic and next-gen projects in various ways. It would be a shame to not be able to have tickets from a next-gen project in a classic board (and vice versa) so I hope that doesn't actually happen as you say above.

Gabriele Franck

Hey, Colin

Just to give you some context first, I've mentioned about not using next-gen issues with classic boards because because, at this moment, the next-gen board type, is designed to be simpler than the classic Scrum and Kanban templates, with a single board, a basic workflow and no schemes or configurations that makes admins lost precious time. It's ready to be used.

So, yes, you will be able to see issues from your next-gen projects in classic boards as long as you have a JQL criteria that include them over there, but although the next-gen is an easier board to deal with, a lot of features from classic boards are not available there for now, you can see that in our Next-gen roadmap for Jira Software Cloud documentation. This can be a little "frustrating" to customers like you that like the idea of customising boards, etc.

Regarding customize cards in next-gen projects, we have a feature request for that here: Ability to customize cards in next-gen projects and from our next-gen roadmap page you can also see that our dev team is already working to make Card Layout available as the first step to letting you customise the card layout.

Let me know if I was able to make things more clear for you now!

Gabi

Colin Hendricks_yn2e8d

Great. Thanks for the details!

Emily Chan

Hello @Colin Hendricks ! We saw that you are using both Classic projects and Next-Gen projects for your organisation. Would you help us learn more about you and your use cases? A one-hour chat with you would be immensely helpful, and we’ll send you a $100 gift card as thanks. If you’re interested, please email me at echan@atlassian.com.

Ray Whiting_uq0iof

I know this is a fairly niche request/need but I also would like to be able to see team-managed custom fields on company-managed boards. We have T-shirt size estimate as a custom field across multiple team-managed boards. We use a board in a company-managed project for a high-level view of Epics across multiple team-managed projects (this works really well), and it would be lovely to see our T-shirt size custom-fields displayed as on the cards on the company-managed board.

There are probably multiple ways of solving this (E.G. enable the above, enable team-managed projects to use the global custom fields, enable multiple boards in team-managed projects to pull issues from multiple team-managed projects AND have card configuration).

I default to team-managed projects and the benefits of lightweight and easy team configuration outweighs the restricted feature-set (almost) every time; but... just sometimes there's a specific thing which I miss (like this)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software