Customizing the issues in a project 1

Issues are the packets of work that need to be completed in a project. These issues are made up of issue fields, and the issue fields contain data about the issue. This data is important, as it helps define the issue, and can contain important information about the issue, such as a summary, a description, due dates, and when and where the work is required. JIRA Software allows you to customize issues by changing the configuration and behavior of these fields to suit your team's needs.You may choose to:

  • Change a field's behavior (such as change a field's description, make a field hidden or visible, or make a field required or optional)
  • Add your own values for fields that have default values assigned (e.g. Resolution and Status)
  • Create new 'custom' fields
  • Configure different renderers for (some) fields
  • Position fields on a screen
  • Choose which screen should be displayed for each issue operation (e.g. 'Create Issue', 'Edit Issue') or workflow transition (e.g. Resolve Issue, Close Issue)

A simple example of how customizing an issue could benefit your team could be marking fields as 'Required' when an issue is created. This would ensure you always capture the required information you need to get the work done to resolve the issue. If you couple this with positioning the required fields at the top of the screen, and even hiding fields you know the issue creator won't use, you'll make sure your users can see and complete the required fields as quickly as possible.

You can make this...

into this...

To customize your issues, you need to be a JIRA administrator. You can review more conceptual information on customizing issues in the JIRA administrator's documentation.

Last modified on Aug 17, 2017

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.