How to Configure Field Configurations in Jira | Atlassian Jira
HTML-код
- Опубликовано: 25 июл 2024
- In this #atlassian #jira video, I am going to teach you about field configurations and how to use them to help you solve conflicts between teams' required fields. Configuration fields are one of the more complex things in Jira. As an administrator, misconfiguring field configurations is probably the easiest way to get into trouble. Watch this guide before you start making changes to your field configurations. This is especially true if you if you try to make a field required only to find out that field is now required for everyone across your Jira instance. Bookmark this tutorial and make sure you can easily reference it later.
If you like this video, please make sure to give it a thumbs up. If you haven't already, please consider subscribing. If you have any questions about anything discussed so far, please feel free to make sure you leave your question in the comments section.
Jira Merch:
linkpop.com/apetech
Link to my other Atlassian Jira videos
• Jira Tutorials
Link to my Atlassian Live Streams:
• Jira Community Live St...
Link to Atlassian's Jira products:
www.atlassian.com/software
Link to my Fiverr profile:
www.fiverr.com/alexortiz924?u...
Link to my Upwork profile:
www.upwork.com/freelancers/~0...
Link to my personal website
www.apetech.me/
You are a life saver, thanks so much for sharing this amazing content!
Awesome video thanks!
you are a legend. i was about to break jira before i saw this. Thank you
I'm glad the video helped you out. Field configurations are probably one of the more confusing things about Jira.
Just love your approach to differentiate field configurations by issue types. It is a little more work at the beginning but, as almost always in life ;-), it saves you hours later on...
I aim to please!!
You made it look so simple, thanks a lot for the video.
I don't use this in 99.9% of cases and the reason for that is that I don't design the system to be a teacher, that is what training is for. If someone wants a field to be mandatory, then I'll add the check in the workflow and never, ever have anything mandatory on create. The reason for that is that it will break integrations and the ability to move from other projects. For Renderers, I'll just make a global decision and then that is what you get. 99.9% that would be Wiki rendering because that is what most want :)
I don't think it is overkill to always make the changes towards an issue type. That is the standard as far as I see it, even if the team only have just one workflow and that is to future proof things.
Great video as always Alex!
Thank you for this video!
This is indeed tricky without you to explain it, you saved me a lot of time ! btw really good teaching. Thanks
Glad it was helpful!
thiss is amazing
Thanks for the video, this helped me a lot. I'm new to Jira Admin stuff.
Hope you found it useful. I'm going to be launching a Jira Admin course on Feb 28th! Let me know if you are interested.
Very helpful video and easy to understand. I noticed when you are in Project Settings -> Fields you show 2 field configurations associated with the project. When I select Use a different scheme, whatever I select overrides the exisiting field confirguration associated with the project. Therefore, I seems as though I cannot have more than 1 field configuration associated with a project.
This will be a problem because I've created field configurations and field configuration schemes for each issue type and want to implement all of them across different projects.
Thanks for the assist!
The multiple field configurations need to be applied to the field configuration scheme (broken up by issue type) and then that entire scheme ( with the multiple field configurations) are applied to the project.
Thank you for making Jira easier to understand, your videos are gold! One question: if I create a couple of custom fields for bug and story issue types (some required, some not) that are specific for these issue types, and I want to make them default for all the company projects (both existing and future ones), should that be done via field configurations or screen schemes?
It is via field Configuration. When you create a custom field, you create it in the field configuration. If you want it to be required you do it via the field configuration, and attach the screens to that particular custom field. I hope that answers your question.
Both. You'll need to do the screen schemes so that the issues show up. And then the field configurations so that they are required.
Thank you for this video!
Question.. Can you have different issue types within the same project where those issue types have different screens/fields that are shown?
I always love the way you talk about your experience, that way you really helping out newbies like me who are looking for to figure out not just Jira settings but they way we should organize things without getting into trouble. Specially who are finding way to learn and apply right away. Thank you so much for plying big part of my Jira learning journey. Really appreciate it. ❤
Is it possible to add those configurations also in Jira Work Management project?
If you make a Company-Managed Jira Work Management project. . . I think it should be possible.
Thanks for the video. Please how many people does a scrum master share report with, 2. What is contained in the report 3. Are the reports shared as a file or just the jira link?
umm, you can share the report with whoever you want. You get to decide what you put in the report. A link is shared only.
hi , where we can set the value of a "Configuration field" i don't talk about "Custom field"
Are you talking about a default field like Description? Some default fields still show up in the custom fields section. If they do show up, you can set a default value. Otherwise, I don't think it's possible.
We thought that Field configuration of Jira Software and Jira Service Management were NOT the same. But it is! Wanting to erase a field in J-Software we broke the issue screen in J-Service Management :D
That's interesting. I wouldn't have thought for that to be the case since the JSM project has it's own field configuration. I'll have to try it out and replicate. Might be a good topic for a future video!
@@ApetechTechTutorials That'll be awesome!
Why not just assign the field to specific project screens? what would be different in your approach?
This specific video was about about the field configurations which is different than adding fields to the screen. The main reason you want to follow the instructions in here is when you want to make a field required using the field configuration. .. . not adding a field to a project.