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.
I am sorry, but I do not understand the question.
Yes, I see you use some custom fields for classes of service (a lot of us do, custom fields are intended to hold data like that). I am not sure what that has to do with "Kanban features". I do not understand what you expect from "classes of service (risk profile)".
You say "We're are wondering if the decisions are * flowing* through well trained staff." - are you asking if Atlassian have product owners who gather information about how people want the products to work that they then roll into the products (they do), or about reporting on how decisions are made and recorded in your own Jira system?
>Custom fields only to issues type do not make any sense!
They're not just to issue types, you can configure them by project, issue type, both, or global. Are you asking for "project level custom fields" and/or "user level custom fields"? Or am I barking up the wrong tree there?
We're more than happy to help you here if you're missing something or struggling to make Jira do what you need, but my lack of understanding is blocking me from saying much. Sorry I'm not getting it!
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Celso Martins , me again. :-) Just an fyi that the Community is primarily served by users like yourself. You may find using the Feedback link in the application to be a better way to provide feedback.
Regarding this question i'm not sure I am following you. Are you one cloud or server? What do you mean by global custom fields? I will try to assist if I can.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jack Brickey and @Nic Brough -Adaptavist-
This time I wanted to send you both a word of praise for your patience in replying to questions with very little content in them. Thank you for supporting this Community.
I am trying, just like yourselves, to support this commmunity when I can but it strikes me every now and then how negligent some people are in supplying details which are necessary for others to give help. I really do not intend to be judgmental here. Some people are better in writing and some are not. However, the fact is that so many times I wanted to help but I must admit that 'guessing' what the person probably had in mind puts me off and I do not reply a word. There will be more people like me (I guess)
I am sure that in many cases it is not a situation when people are 'lazy writers' but rather not aware how to ask questions properly. Maybe you, community leaders, could write a short "Before you ask for help" article and stick the link to it somewhere on top of the Community page. Something like a guideline: context: your goal you wanted to achieve - what you did in the system - what you expected to happen - what actually happened - your question.
I think this might be a good investment of your time and hopefully the whole Community will have less questions unanswered.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.