Top 5 Custom Fields Every Jira Application Needs
Atlassian, an Australian company, has developed the JIRA tool. The software is generally used to track bugs and for the management of different projects. The exciting thing is that JIRA has been taken from a Japanese word -Gojira – which means Godzilla.
The software helps to track any issues or bugs related to mobile and software apps. The software’s dashboard deserves special mention as it has several useful functions that facilitate smooth handling of various matters. The primary job of a Jira administrator is to choose the Jira custom fields carefully. We recommend that the following five custom fields are useful and should be created.
Sometimes one needs to associate the issues in Jira with records in other offline applications, for example, an ID in the vendor system or a serial number in a piece of equipment. Since individual custom fields are often overused, it is advisable to create a single line Text Field and name it as IDs. The users are encouraged to enter ID numbers, but commas must be separating them.
Everybody knows that Jira’s issues are connected with data from external websites and the various applications developed within the company. The Development team, for example, can ask for links to vendor citations. The Facilities team can request a specific link related to big equipment orders. The Human Resource team might need to create a connection between employee records to a 3rd party employee resource app.
Linking in Jira becomes a lot easier when the external apps are integrated within the software. But what happens with the other apps that are not connected? Well, for them, one has to create a multi-line Text Field, & name it as URLs. The users can put in an indefinite number of links that connect them to further online areas. The Jira software will make the URL clickable on the View screen of the issue.
Your main job is to find out the department’s name that generates the team’s maximum number of requests. However, Jira is not aware of the user’s department name or team name, or the manager’s name. While it is possible to store that data, there is no way you can go ahead and leverage that data with no custom development. So create a single line field, and then name it as Department.
This field type is very similar to the department. One will have to create a single choice field and then name it as Team. One can also put the Department and Team in a single field by using the cascading select list type. The user will first choose a department, and the team is chosen from another set of selections.
The Components field is one of the best ways to classify and automatically assign job. If you require a 2nd categorization method, one can create a multiple-choice based Select List field & then name it as Category. It is a generic name but has its importance as it can encompass many scenarios.