When using a git-connected project with a feature-branching strategy you will notice that your requirements page is in read-only mode. This is because it acquires the features to display from the feature files in your feature file directory, on your base branch.
The acceptance criteria shown in these features can be changed by editing them within the attached Jira issue. This will update the feature file that Behave Pro produces and will be pushed to the Jira issue's feature branch, it will have the format of:
This branch can then be merged into the master branch to be viewable within the requirements page.
The requirements page can be edited directly in a Classic project configuration or alternatively by using a trunk-based branching strategy with Git.