Remove the (Feature path) field from the "project" content type

Created on 14 August 2023, over 1 year ago
Updated 23 August 2023, over 1 year ago

Problem/Motivation

Do not need the (Feature path) field in the "project" content type, cause it will be a Gherkin area field to write instead of uploading a ".feature" file.

Proposed resolution

Remove the (Feature path) field from the "project" content type.

Remaining tasks

  • ✅ File an issue
  • ✅ Addition/Change/Update/Fix
  • ➖ Merge request, Patch, or Commit
  • ➖ Testing to ensure no regression
  • ➖ Automated unit testing coverage
  • ➖ Automated functional testing coverage
  • ➖ UX/UI designer responsibilities
  • ➖ Readability
  • ➖ Accessibility
  • ➖ Performance
  • ➖ Security
  • ➖ Documentation
  • ➖ Code review by maintainers
  • ➖ Full testing and approval
  • ➖ Credit contributors
  • ➖ Review with the product owner
  • ➖ Release notes snippet
  • ❌ Release

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • N/A
📌 Task
Status

Fixed

Version

10.0

Component

Code

Created by

🇯🇴Jordan tasneem natshah

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024