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

Cucumber feature REST API - support for required fields

    XporterXMLWordPrintable

Details

    • Story
    • Status: Closed
    • Major
    • Resolution: Done
    • None
    • 1.008.000
    • REST API
    • None
    • R1.008.000 S3, R1.008.000 S4
    • OK

    Description

      Cucumber feature REST API - support for required fields

      Allow adding values for issue fields/custom fields when using the cucumber feature REST API. (import/feature)

      If Jira is configured with required fields for the Test Issue type it won't be possible to use this endpoint as it is currently not possible to provide values for these fields in the REST API request.

      ACs:

      • The "Import Cucumber Tests" endpoint for importing feature files must provide two a new parameters for JSON files to be used as a templates for creating new Tests and Pre-Conditions respectively.
      • Xray must support a new parameter named "testInfo" to pass the JSON file containing the fields for creating Tests.
      • Xray must support a new parameter named "preCondInfo" to pass the JSON file containing the fields for creating Pre-Conditions.
      • The JSON file format is the same as Jira uses for the REST API (https://docs.atlassian.com/software/jira/docs/api/REST/8.2.0/?_ga=2.111455874.746998918.1558343025-232874918.1557136424#api/2/issue-createIssue)
      • The "Summary" and "IssueType" fields will be ignored by Xray.
      • The "parent" field also makes no sense, as Tests and Pre-Conditions can't be Sub-Tasks. Xray will ignore this field as well.
      • Xray will return any error originated in Jira when creating Tests or Pre-Conditions.

      Attachments

        Issue Links

          Activity

            People

              ampr Andre Rodrigues [X] (Inactive)
              cgso Claudio Sousa
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 10 minutes
                  1d 10m