What did you do with the global custom fields?

Question

We use custom fields to map classes of service, yes you've created Kanban features but did not add classes of service (risk profile). We're are wondering if the decisions are * flowing* through well trained staff.

Custom fields only to issues type do not make any sense!

Please correct that.

Thanks.

Nic Brough -Adaptavist- · Answer

Sorry for the delay on this, it dropped out of my list.

Yes, this helps explain what you're looking at.  Next-gen projects are a totally new way to set up projects, and have been designed without re-using the ideas from "classic" projects much.

It is, allegedly, what most people want according to Atlassian's UI and persona research.

Celso Martins · Answer

Please look into @Nic Brough -Adaptavist- 's thread.

Thanks

Celso Martins · Answer

Hey @Nic the issue is very simple. We are creating custom field to map class of service (risk profile) in Kanban flows. But we can only create a custom field to a type of card (one for bug, for feature, and so on). The result is:

Bug -> Class of service: Standard
                         Expedite
                         Fixed Date
                         Intangible

Feature -> Class of service: Standard
                             Expedite
                             Fixed Date
                             Intangible
Chore -> The same

It happens only in new gen projects. When we are using classic projects, we are able to create custom fields to entire jira account and use them in projects.

I hope it is more clear now.

Thanks for your reply. It is another must to have to new gen. But we're not impacted anymore since all of our customers are migrating back to classic projects.

Best.