Assigning priority to test artifacts

Users can assign a priority to individual test artifacts. As an administrator, you can edit the literals (labels) for the existing priorities and define a new priority. Any new priority that you create has a value greater than the selected priority.

1. Log in as one of the following users who has the appropriate permission to save project areas:
   • A user granted permission to save the project area in the process configuration.
   • A user who is an administrator of the project area.
   • A user who is granted either the JazzProjectAdmins or JazzAdmins repository group permissions.
2. In the banner, click the Administration () icon and click Manage This Project Area.
3. In the Project Area editor, click Test Artifacts > Priority.
4. Optional: Select a new literal for the default test artifact priority.

   The default priority literal is set to Unassigned. You can change the default to another value.

5. To change any of the existing literals, click to select an existing literal, type the new literal value, and click Save.
6. To define a new priority literal, select the row for an existing literal (Low, Medium, or High) and click Add.
7. When asked if you want to create a priority literal whose value is greater than the priority of the selected row, click Yes.
   For example, if you select Low, you are adding a priority literal whose value is greater than Low, but less than Medium.
8. In the Add Priority Literal window, type a name for the new literal, such as Low-Medium.
9. Optional: Specify an external URI to identify a literal across Engineering Test Management projects.

   Within a project, you might use an external URI for each literal. If another project has an equivalent literal, use the same external URI of the equivalent literal to ensure consistency across Engineering Test Management projects. Jazz Reporting Service (JRS) uses the external URIs to map literals that are equivalent to each other. Equivalent literals might have different names or enumeration values across Engineering Test Management projects, but if you assign the same external URI to these equivalent literals, they are treated equally when you create reports across Engineering Test Management projects. It avoids the need to set filters for each of the literals when you create reports across Engineering Test Management projects. To specify the external URIs, use the following format:

   [scheme:][//authority][path][?query][#fragment]

   For example:

   "http://xyz.com/path?validate=how"

   For more information, see Integrating external data sources with Lifecycle Query Engine and Report Builder.
10. Click Browse, select an icon to assign to the new literal, and click OK.
11. Click Save.