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

As a user, I want to edit the Testing Board and add custom columns

    XporterXMLWordPrintable

Details

    • Suggestion
    • Status: New
    • Resolution: Unresolved
    • None
    • None
    • Column Layout, Testing Board, UI
    • None
    • UNCOVERED

    Description

      Users currently cannot customize the structure of the Testing Execution Board and Testing Board. This limits flexibility in adapting boards to different workflows, testing phases, or team-specific needs. Allowing users to add and modify custom columns would enable better tracking, organization, and visibility of testing activities. Uer should be able to edit the Highlighted area.

      User friction

      • Users are forced to work within a fixed board structure
      • Inability to reflect real testing workflows (e.g., “Blocked”, “Ready for Retest”, “In Review”)
      • Manual tracking outside the system (e.g., spreadsheets, notes)
      • Reduced efficiency and clarity in test execution tracking 

      Steps to reproduce (right now) / Actual Result:

      1. Navigate to Testing Execution Board or Testing Board
      2. Attempt to modify existing columns or add a new column
      3. Observe that no option exists to customize columns

      Actual Result:
      Users cannot edit, add, or remove columns; board structure is static

      Impact

      What would improve if solved:

      • Increased flexibility to match real-world QA workflows
      • Better visibility of test progress and statuses
      • Reduced need for external tracking tools
      • Improved team productivity and collaboration 

      Impact on stakeholders:

      • More efficient test tracking and status management
      • Clearer overview of testing progress
      • Improved transparency into testing lifecycle
      • Higher adoption due to customizable workflows 

      Current workaround:

      • Using external tools (e.g., spreadsheets, Kanban boards) to track additional states
      • Overloading existing columns with multiple meanings

      CONTEXT & EXAMPLES:

      Concrete example:

      A team may have a custom field such as Security Validation Required or Time tracking, and they would like to display it directly on the Testing Board for faster execution decisions.

      Workaround risk:

      • Miscommunication of test status
      • Loss of important workflow granularity
      • Increased manual effort and human error
      • Fragmented tracking across tools

       

      Attachments

        Activity

          People

            bernardo.cottim Bernardo Cottim
            tripti.kumari Tripti Kumari
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 30 minutes
                30m
                Logged:
                Time Spent - 0 minutes
                0m