Uploaded image for project: 'Xray for Jira Cloud'
  1. Xray for Jira Cloud
  2. XRAYCLOUD-10881

Test Repository Grid should have more columns

    XporterXMLWordPrintable

Details

    • Suggestion
    • Status: New
    • Resolution: Unresolved
    • None
    • None
    • Test Repository
    • None
    • Xray Cloud

    • UNCOVERED

    Description

      Description

      In Xray, the Test Repository grid should offer customizable columns to display more fields related to each particular test directly within the repository view. Currently, the visible columns are limited, forcing users to click and navigate into each individual test issue to view critical information. Users should have the ability to configure and add additional test-specific columns directly in the Test Repository page.

      User friction

      • Teams managing large tests waste massive amounts of time constantly clicking back and forth between the repository folders and individual test issue views just to check basic details
      • Every time a user is forced to leave the Test Repository screen to check a field, they lose their place and their filtered context within the folder structure.

      Steps to reproduce (right now) / Actual Result:

      • Navigate to the Testing Board and open the Test Repository.
      • Select a folder containing multiple Test issues.
      • Observe the available columns in the repository grid view.
      • The grid view displays minimal columns (e.g., Key, Summary). There is no option to add columns for other essential fields

      IMPACT

      What would improve if solved:

      • Significantly speeds up test planning, triaging, and review cycles for QA teams.
      • Enables users to maximize their view by tailoring the data columns to their team's specific in Test Repository itself.

      Impact on stakeholders:

      • Can quickly scan and organize tests within a repository folder based on parameters like Priority.

      Current workaround:

      There is no configuration option within the Test Repository UI, but we can use the Test List report from the Reporting center.

      CONTEXT & EXAMPLES:

      Concrete example:

      A QA team structures their Test Repository by feature folders. Within a "Login Feature" folder, they have 50 tests, some automated and some manual. They want to see all the values and fields for the Test inside the test repository at the same time.

      Workaround risk:

      NA

       

      Attachments

        Activity

          People

            bernardo.cottim Bernardo Cottim
            kiran.kumar C Kiran Kumar
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: