How to Create a New Issue Screen Scheme for the Testing Issue Type in Jira

Overview

In Jira, Screen Schemes are used to define which screens (Create, Edit, View) are associated with different issue types. If you want to create a custom screen setup for a specific issue type like Testing, you can define a new Issue Screen Scheme and associate it with that issue type. This article provides step-by-step instructions on how to create a new Issue Screen Scheme specifically for the Testing issue type.

Steps to Create a New Issue Screen Scheme for Testing Issue Type

Step 1: Create a New Screen

Screens in Jira are used to define which fields are displayed during the creation, editing, or viewing of an issue. We first need to create a custom screen for the Testing issue type.

  • Navigate to Jira Administration:
  • Click on the gear icon (top-right corner) and select Jira Settings.
  • Under the Issues section, click on Screens.
  • Create a New Screen:
  • Click the Add Screen button.
  • Enter a name for your new screen, such as Testing Issue Screen. This screen will be used specifically for the Testing issue type.
  • Optionally, provide a description for the screen (e.g., Screen for creating, editing, and viewing Testing issues).
  • Click Add.

Step 2: Add Fields to the Screen

Once the screen is created, the next step is to add fields that should be visible when creating, editing, or viewing a Testing issue.

  • Configure Fields for the Screen:
  • After creating the screen, click Configure next to the screen you created (e.g., Testing Issue Screen).
  • You will see options for the following screens:
  • Create Issue Screen: Fields that should appear when creating a Testing issue.
  • Edit Issue Screen: Fields that should appear when editing a Testing issue.
  • View Issue Screen: Fields that should appear when viewing a Testing issue.
  • Add the Required Fields:
  • Select the fields you want to display on the Testing issue screen. Some common fields for testing might include:
  • Summary
  • Description
  • Assignee
  • Priority
  • Severity (if you have a custom field for Severity)
  • Labels
  • Test Steps (if custom)
  • Test Results (if custom)
  • For each screen (Create, Edit, View), click Add Field and select the appropriate fields.
  • After adding the fields, click Save.

Step 3: Create a New Issue Screen Scheme

Now that you have created a screen with the necessary fields, you need to create a Screen Scheme that will associate the screen with the Testing issue type.

  • Navigate to Screen Schemes:
  • In Jira Settings, go to Issues > Screen Schemes.
  • Create a New Screen Scheme:
  • Click on Add Screen Scheme.
  • Enter a name for the new screen scheme, such as Testing Issue Screen Scheme.
  • Optionally, add a description (e.g., Screen Scheme for Testing Issue Type).
  • Click Add.
  • Associate Screens with the Screen Scheme:
  • Click on Configure next to the new Testing Issue Screen Scheme.
  • For each action (Create, Edit, View), select the appropriate screen from the dropdown (in this case, select Testing Issue Screen for all actions).
  • Create Issue: Choose Testing Issue Screen.
  • Edit Issue: Choose Testing Issue Screen.
  • View Issue: Choose Testing Issue Screen.
  • Click Save after configuring all screens.

Step 4: Create or Modify an Issue Type Screen Scheme

An Issue Type Screen Scheme maps issue types to a specific Screen Scheme. You need to associate the Testing Issue Screen Scheme with the Testing issue type.

  • Navigate to Issue Type Screen Schemes:
  • In Jira Settings, go to Issues > Issue Type Screen Schemes.
  • Create a New Issue Type Screen Scheme:
  • Click on Add Issue Type Screen Scheme.
  • Enter a name for the scheme, such as Testing Issue Type Screen Scheme.
  • Optionally, provide a description (e.g., Screen Scheme for Testing issues).
  • Click Add.
  • Associate the Screen Scheme with the Issue Type:
  • Click on Configure next to the Testing Issue Type Screen Scheme.
  • Under Issue Type Screen Scheme, you will see a list of available issue types.
  • Find the Testing issue type (create one if it doesn’t already exist) and select the Testing Issue Screen Scheme for that issue type.
  • Click Add to associate the screen scheme with the issue type.

Step 5: Associate the Issue Type Screen Scheme with a Project

Once you’ve configured the Issue Type Screen Scheme for the Testing issue type, you need to associate it with a project.

  • Navigate to Project Settings:
  • Go to the Project Settings page for the project where you want to apply the new screen scheme.
  • Modify the Screen Scheme for the Project:
  • Under Project Settings, go to Screens.
  • Click Actions > Use a Different Scheme or Edit Configuration.
  • Choose the Testing Issue Type Screen Scheme (the one you created earlier) and save the changes.

Step 6: Test the Configuration

Once the screen scheme is applied, it’s important to test and ensure that it is working as expected.

  • Create a Testing Issue:
  • In the project where you applied the new screen scheme, create a new Testing issue.
  • Verify that the Testing Issue Screen is displayed during issue creation.
  • Edit and View the Testing Issue:
  • Edit the issue and confirm that the Testing Issue Screen appears in the Edit Issue view.
  • View the issue and ensure that the correct fields appear on the View Issue Screen.

Conclusion

You have successfully created a new Issue Screen Scheme for the Testing issue type in Jira. By following these steps, you have customized the screens to show specific fields when creating, editing, or viewing Testing issues.

This configuration allows your Jira project to display the necessary fields tailored to Testing-related tasks, improving the overall user experience and issue management.

Further Customization (Optional)

  • Add Custom Fields: If you have custom fields like Test Steps or Test Result, you can add them to the screens created for the Testing issue type.
  • Workflow Customization: You can also associate workflows specific to the Testing issue type, ensuring that transitions and statuses are tailored to the testing process.
  • Permissions and Notifications: Ensure that only the appropriate users can view or edit specific fields on the screens by configuring field permissions and workflow post-functions.

Leave a comment

Your email address will not be published. Required fields are marked *