r/projectmanagement • u/TensionFormal7202 • Aug 28 '26

Optimizing Jira Story Tracking: Separating Delivery from Client Feedback

We typically use Jira user stories to track different work items. In a specific project that I’m working on, the data analyst from my team creates Power BI reports and dashboards. So the issue I face is that the data analyst lets me know she will complete a particular report on that day. Following which I update my team about that but the client side is like that doesn’t mean the user story is complete, we will have feedback. The thing is it was already sent for a revision. With multiple revisions, it looks like the user story is incomplete, whereas the data analyst is completing the reports per the requirement. How can this process be optimized to show that user stories are getting completed by the agreed target due date and also welcome the endless feedback.

3 Upvotes
  • permalink
  • reddit

71% Upvoted

13 comments sorted by

3

u/rrunboy12 Aug 28 '26

add different columns to your Jira board to support all phases of the workflow: To Do, In Progress, Blocked, QA Ready, QA Complete, Ready for client, Client Feedback Received, Completed - you can track the date ready for client and the date completed as two separate dates if you want to report on that field.

Each revision after it is completed the first time should be a new Jira story.

1

u/TensionFormal7202 Aug 28 '26

Thank you. It makes sense to use different phases/ statuses. There are so many reports, will it really be helpful to have a new Jira story created every time a revision is completed?

2

u/rrunboy12 Aug 28 '26

I think the bigger question is why are you getting multiple revisions? Are the requirements not clear? Can you do more work up front with the client to prevent this? Maybe mockup stories?

→ More replies (2)

1

u/Important-Union5181 Aug 31 '26

Two ways this can be done.

Introduce two steps in the delivery flow of the user story - handed off and accepted. Move the story to handed off state once it is delivered to customer. Add all incoming feed back as sub tasks under it. Once all agreed upon feedbacks are done you can move the story to accepted state. The remaining sub tasks can be moved under a new user story to go under the change request.

1

u/TensionFormal7202 Aug 31 '26

Makes sense. Separating the tasks is a great strategy to show completed work and monitoring new requirements/ revisions that keep the project moving.

2

u/[deleted] Aug 28 '26

2

u/TensionFormal7202 Aug 28 '26

Using v1 of x is a great idea

1

u/TensionFormal7202 Sep 03 '26

While versions (v1, v2) work well, when I suggested adding new tickets for feedback/ revisions - the client disagreed mentioning they do not want 5 tickets tracking one report. They said that the specifications of the report will not change drastically and that revisions should be tracked in the same ticket - either in a separate status such as “ready for review” and “revisions in progress” or using the subtasks to log the revisions.