Xray - Naming convention to distinguish test plan, test execution, test sets, and test case

[CHRISTOPHER QUIDLAT]

Is there a best practice around naming test issuetypes (test plan, test execution, test set, test) ?  

[Francisco Fonseca _Xray_]

Hi @CHRISTOPHER QUIDLAT ,

Welcome to the community!

Just to clarify, are you referring to naming conventions when creating a Test Plan, or are you asking about renaming the issue type itself, such as changing “Test Plan” to something else?

Regarding naming conventions for Test Plans as an example:

There’s no universal “right” answer. The naming should reflect how your team organizes its testing strategy. For example:

• If you’re working within a sprint-based methodology, your naming might look like: “Sprint 1 - Regression”.
• If you’re organizing by test type (Regression, Performance), you might consider including components or specific scopes like: “Login - Performance Tests” or “Checkout - Regression”.

Ultimately, the goal is to choose a naming convention that mirrors your internal structure and makes it easy to understand, track, and filter Test Plans in Jira.

As for renaming the actual issue type, for example, changing “Test” to something like “Test Xray”, we usually don’t recommend it. If you ever need to migrate projects or integrate with external tools, having custom issue type names can complicate the process. You’d need to map those custom names carefully to ensure consistency and data integrity.

Check out our Tutorial for process here, might be helpfull.

Best, Francisco

[CHRISTOPHER QUIDLAT]

Thanks, I meant naming conventions when creating Test Plan and the other issue types.  

What we've found to be challenging when using XRay is that when you're deep down the process of creating test plan, linking a test execution to the test plan, selecting a test set for a test execution, these test components - test plan, test execution, test set, and test - become so difficult to distinguish.  You don't know whether you're editing a test set, test execution, etc.  The icons that accompany the components are not intuitively recognizable.  

I was wondering if you have seen any practices like including a prefix (e.g. TP for test plan, TE for test execution, TS for test set, etc.) to distinguish them instantly by issue type without the need for icons or anything else. 

[Josh]

Also interested in this answer...