![]() ![]() For example, you have your fields Context must be set up to allow that Project and Issue Type, your Field Configuration must be set up to show that Field, and there must be a Screen with that field present attached to that Issue Type. ![]() Three separate configurations must be set up correctly for you to see a field within a project. So, you’ve created some Custom Fields and are trying to get them attached to a project. A Field’s Context, Field Configurations, and Screens…I mean, what even? I’ll go into ways to accomplish this and still have different settings per Project later, but it’s a massive headache for everyone if you have multiple fields with the same name. It’s up to you not to be the rubber stamp and provide some scrutiny for the sake of your Jira instance.Īlso, as one last note, every custom field should be uniquely named. Even with a shopping list available, you will get requests for similar fields. I would also make it a point to go through your Custom Field list every time you get a new Field Request to make sure a similar one doesn’t already exist. Having this list will allow them to requests fields that are already in your instance rather than request new ones all the time. Encourage them to use it as a “Shopping List” for custom fields. This way, it can be re-used for more than just the ABC Project.Īnother thing you should do is you should have a current list of Custom Fields in your Documentation and make sure it’s accessible to End Users. I would reject this and propose we call it “End Date” instead. For example, let’s say you get a request asking you to add a Custom Field “ABC End Date,” where ABC is the Project Key for a specific project. To start with, I would suggest you keep your Custom Field names as generic as possible. So, as a best practice, you should have some governing around how Custom fields are added to your system. This fact is because it will depend on your system’s architecture, performance metrics of things like Network and Database, and even how far away most of your users are from your Jira system. Unfortunately, it’s hard to give you a concrete answer as to how many is too many. ![]() ![]() However, just like having too many sweets, including too many custom fields to your Jira instance can cause serious problems. They are a great way to add some functionality and usefulness to your Jira Instance in small batches. I like to compare Custom Fields to candy. For example, Jira Software adds several Locked custom fields used for it to function correctly. Be aware that some of these fields are autogenerated by Apps and Applications. You can find the list of the current Custom Fields by going to your Admin Section -> Issues -> Custom Fields. Having custom fields is vital to ensuring your teams can capture the information they need to do their job and then organize, sort, and report on that very same data. The custom part means you, dear Jira Guys and Gals, get to define what they are, how they behave, and how they look. So, for the most part, you are stuck with them – but that’s okay.īut then there are the custom fields. Unfortunately, these fields cannot be customized or changed in any significant way. These are entries like Description, Summary, and Due Date. First, there are the System fields that come with Jira Core out of the box. In general, there are two types of fields in Jira. Anything you can enter on an issue is considered a field. Jira, being Database driven, borrowed this term to refer to each entry within a given issue. So, what are custom fields?Ī field, in Database terms, is a piece of categorized information within an entry or row. So I figured I’d spend today doing a deep dive into Custom fields, what they are, how they can be used, and what some of the best practices are around them. Do you know what I think is one of the most misunderstood features of Jira also is? Yep, custom fields. Based on the number of tickets and requests I had for it over the years, do you know what I think the most loved feature of Jira is? Custom fields. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |