Sprint Board Reporting - reporting status of a specific data field that is held in 1 Story

Question

Currently we have Sprint Board 'A' - which contains a Story ticket for each Requirement and circa 10-15 sub-tasks associated to it.  Each subtask tracks the production of an artefact and or completion of an activity required to delivery the sprint goals.  Across the project we are creating 100's of tickets - but we are able to monitor & report on their progress via a series of JQLs  in Confluence - so all is good.

There is an ask for us to assess how we can reduce the number of sub-task tickets that are created  - without losing our ability to monitor.

A thought is,

We create a single Story ticket for each Requirement due delivery and, within that, have a series questions with a dropdown selection e.g.

Has action A been completed?

- YES

- NO

- Not Required

This is repeated for each artefact/activity required AND replicated within each Story.

My query is.

Is it possible set a JQL query which checks each Story held within the sprint board and queries a defined activity within the Story?

i.e. Tickets where "Has action A been completed != YES"  - then present the results  - to  allow this to be reviewed and followed up?

Apologies for the long nature of the question but buy JQL skills have been exhausted and I thinking this is not possible!

Andrew Wilks · Answer

Thanks for your response  - after reviewing your counter questions and doing some prototype testing - we have determined that a review of the volume & necessity of subtasks we create rather than looking to replace all with a single ticket.

Andrew Wilks · Answer

Thanks for your response  - after doing some prototype testing of the various options  - we have determined that a review of the volume & necessity of subtasks we create rather than looking to replace all with a single ticket.

Bill Sheboy · Answer

Hi @Andrew Wilks -- Welcome to the Atlassian Community!

You note this:

There is an ask for us to assess how we can reduce the number of sub-task tickets that are created  - without losing our ability to monitor.

What is the problem being solved by reducing the number of sub-tasks?  That is, "why" do that?  Knowing this may help the community to offer better suggestions or alternatives.

Jira is essentially a work-management tool, and your team seems to be using sub-tasks effectively to manage work.  Other methods can be used to reduce sub-task usage for your scenario, but they will likely have unintended consequences.  Understanding the problem being solved will help to understand that better.

Kind regards,
Bill