...
Depending on your preferences menu options the Feature panel might be loaded in Gherkin Text Editor mode rather than Example Mapping, so you will see textual representation rather like below.
...
| Info |
|---|
Search for issues with Features Query below can be used to find all Jira issues where the Feature panel has at least some text Feature.content IS NOT EMPTY  |
Search for Feature Attributes
The following list of attributes becomes are searchable with JQL:
Feature.userStories
...
| Expand | ||
|---|---|---|
| ||
Feature.userStories = 0 Could be used to identify Jira issues that have some Feature text but are missing key pieces of information such as who the user or the stakeholder is for whom the story is valuable and/or why exactly the story is needed, or in other words ‘As I' or 'So that’ keywords are missing.  Feature.userStories > 1 Could be used to identify Features that contain more than one User Story and therefore should be split into further Jira issues.  |
...
| Expand | ||
|---|---|---|
| ||
Feature.unansweredQuestions > 0 Could be used to identify Jira issues that need further information before they could be developed. 
|
Feature.rules
Type - Number
Description: total number of Rules the Feature contains. There needs to be some text after the Rule keyword in order for the Rule to count towards this number.
| Expand | ||
|---|---|---|
| ||
Feature.rules > 0 Could be used to find Jira issues which have at least some Acceptance Criteria entered. Rules in Features files essentially are the acceptance criteria.  |
Feature.leastScenariosInRule
Type - Number
Description: lowest number of Scenarios contained in any Rule inside the overall Feature
| Expand | ||
|---|---|---|
| ||
Feature.leastScenariosInRule = 0 Could be used to find Issues where there is at least one Rule without any Scenarios  This same query will also include any issues where there is a Rule with Scenarios however there is no text after the Rule keyword (i.e. an empty Rule card), meaning the Rule is not yet defined.  |
Feature.mostScenariosInRule
Type - Number
Description: highest number of Scenarios contained in any Rule inside the overall Feature
| Expand | ||
|---|---|---|
| ||
Feature.mostScenariosInRule > 5 Could be used to find Issues where there are perhaps too many Scenarios in a Rule which could mean that some of the examples could be potentially moved under a new not yet captured rule.  |
Feature.scenarios
Type - Number
Description: total number of Scenarios the Feature contains. All valid scenario keywords are taken into account i.e. Scenario, Example, Scenario Outline or Scenario Template.
| Expand | ||
|---|---|---|
| ||
Feature.scenarios = 0 Could be used to find Jira issues that do not yet have any examples of behaviour  |
Feature.leastStepsInScenario
Type - Number
Description: lowest number of Steps contained in any of the Scenarios inside the overall Feature
| Expand | ||
|---|---|---|
| ||
Feature.leastStepsInScenario = 0 Could be used to find Jira issues where there is at least one Scenario which hasn’t been discussed to the level of concrete steps that would demonstrate the desired behaviour.  |
Feature.mostStepsInScenario
Type - Number
Description: highest number of Steps contained in any of the Scenarios inside the overall Feature
| Expand | ||
|---|---|---|
| ||
Feature.mostStepsInScenario > 5 Could be used to find Jira issues that have Scenarios with potentially too many steps which could mean that the Steps were used to describe ‘how’ functionally was implemented and not ‘what’ behavior was required which is an anti pattern in BDD.  |
Feature.warnings
Type - Number
Description: total number of warnings the Feature contains according to the syntax of Gherkin
| Expand | ||
|---|---|---|
| ||
Feature.warnings > 0 Could be used to find indentation warnings for example  Or missing data table values  |
Feature.errors
Type - Number
Description: total number of errors the Feature contains according to the syntax of Gherkin
| Expand | ||
|---|---|---|
| ||
Feature.errors > 0 Could be used to find incorrectly entered text  Or structurally incorrect data tables  |
Feature.lines
Type - Number
Description: total lines in a Feature
| Expand | ||
|---|---|---|
| ||
Feature.lines > 100  |
Feature.lastUpdatedDate
Type - Date
Description: the time and date the last time the Feature was updated by any user
| Expand | ||
|---|---|---|
| ||
Feature.lastUpdatedDate > startOfWeek() Could be used to find all Jira issues where the Feature was updated since the start of the week  Feature.lastUpdatedDate > startOfDay(9h) Could be used to find all Jira issues where Feature has been updated since 9:00AM of current day  |
Feature.lastUpdatedBy
Type - User
Description: the user who last updated the Feature
| Expand | ||
|---|---|---|
| ||
Feature.lastUpdatedBy = currentUser() Could be used to find all Jira issues where I (current user) was the last to update the Feature  |
Feature.updatedBy
Type - User
Description: any user that made at least one update to the Feature
| Expand | ||
|---|---|---|
| ||
Feature.updatedBy = currentUser() Could be used to find all Jira issues where I (current user) made at least one update to the Feature  |
Built-in Editor Search
When in Gherkin Text Editor mode use the toolbar button highlighted below to open the built-in search pop up box in the top right of the editor. Type a search phrase and press the Enter key - match results will get highlighted in yellow.
...
| Info |
|---|
Folded sections are also searched Using built-in search is superior to using the standard browser find functionally in that it also searches in lines that are currently folded  |