Page Comparison

...

Expand
title Examples
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.

...

Attribute name

...

Type

...

Description

...

Examples

...

Feature.userStories

...

Number

...

How many “complete” User Stories the Feature contains.
Complete in this case means that the User Story entered after the Feature keyword there is some text after the 3 common keywords

Feature.userStories > 1 Could be used to identify Features that contain more than User Story and therefore should be split into further Jira issues. Image Added

Feature.questions

Type - Number

Description: total number of questions the Feature contains. Questions are comment lines prefixed with “Q:“ keyword, see more in Questions & Answers.

Expand
title Examples
Feature.questions = 0 Could be used to identify Jira issues that are potentially completely clear to the development team and therefore ready to go into the Sprint Backlog or maybe those which have not been discussed yet at all. Image Added

Feature.unansweredQuestions

Type - Number

Description: total number of unanswered questions, i.e. those that do not have the 'A:' keyword on line below, see more in Questions & Answers.

Expand
title Examples
Feature.unansweredQuestions > 0 Could be used to identify Jira issues that need further information before they could be developed. Image Added Info Combine attributes You can combine Feature attributes in the same search query to give you more precise results Feature.questions > 0 AND Feature.unansweredQuestions = 0 Could be used to better identify Jira issues that have been discussed with the team and have had all the questions answered and perhaps are ready to go into the Sprint backlog. Image Added