This is the first post of a serie about customization of Tickets on Jira Software.
The default templates of a Jira Project include a list of type of tickets, in order to make it better fit to teams workflow and helps the project management to gather data about the teams workload and their performance, in some cases is needs to customise the tickets template by adding or modify fields.
By adding new fields we can collect specific data needed to generate reports that visualize the actual performance of the teams and it let us spot where it can improve. In many cases these new fields can be filled by the teams but sometimes is better to create automations that fill them and ensure that data is not missed.
On this post I’ll focus on the type of ticket Bug, from my experience this type of ticket can provide us critical information to improve our Incident Management process and likewise it can helps to get actual metrics about the performance of teams and their response to critical scenarios.
Example : Customize an exists ticket, add a field for RFO
For this example, will added a new custom field called RFO, it will be used to enter the Reason for Outage ,is good to know that the RFO is a requirement only for type of ticket Bugs
1- For an standard Jira Project you will have the type of tickets as capture below, select the type “Bug”
2- Jira offer 2 type of fields for texts “Short text” and “Paragraph”, I would suggest to select the Paragraph for this example, just to allow enter more information and format it if is needed, but a Short text field also should be ok
3- On the side bar click on “Create a field” and click on “Paragraph”
3- Drag and drop the new field on Description fields section and set the new field as capture below:
The RFO is a requirement to close a Bug, but is not required for ticket creation, so, don’t set it as required, it can be handle later.
4- Save Changes
5- Open an active bug ticket, the RFO should appear as below
This is the way to add new fields. The RFO is an important information that explain in a simple sentence the cause of the bug. In a upcoming post we will see how to make it required to fill before close a Bug.
No responses yet