Velocity chart is not displaying any data

[sharmila patwardhan]

I have "Ready for UAT", "Done", "Resolved" and "Closed" in the last column. Remaining 3 statuses not mapped this scrum board. I have another Kanban board which are having all three statuses including Ready for UAT status as the first column.

Not All 4 statuses are in DONE status category

Scrum board columns will be like this:

TODO | DEVELOPMENT | TESTING | Ready for UAT

Kanban board columns will be like this:

Ready for UAT | In UAT | Ready for Release | CLOSED

My developers will complete their sprint once all the issues reached in Ready for UAT status.
Then the team responsible for UAT will be taking care rest of the process. They are following Kanban process.
So as and when they receive items in the erady for UAT column they start working irrespective of the sprint. They don't wait for the sprint to complete.

Is there any way to handle it

The current problems are :

1. When I complete the sprint,  velocity is still 0 , all in "Ready for UAT" should ear points here apart from Done, resolved and closed

2. In the sprint report, i dont see a single issue listed as completed

3. even Closed , resolved are getting carried forward and not shown as completed.

Is there something wrong in the way this is done?

[Petter Gonçalves]

Hello @sharmila patwardhan

Sorry to see you are facing some problems.

Please, allow me to provide you with some concepts about the questions you have so we can confirm we are on the same page here:

As you can see in the Velocity Chart documentation, This report is based on your board's column mapping. An issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. Additionally to that, the Sprint will consider an issue to be completed when it is added with a valid resolution and a status in the Done category.

That being said, you must ensure all those three facts are achieved to consider an Issue to be completed in your reports, changing the current flow of your Developers and UAT team. Practically:

1 - Instead of using the same issue to map all the progress from DEV (TODO) to UAT (CLOSED), you can create different issues for each team, using different issue types and workflows to map them:

DEV Issue type:

TODO | DEVELOPMENT | TESTING | Ready for UAT

UAT issue type:

Ready for UAT | In UAT | Ready for Release | CLOSED

2 - Then, use the Issue Link feature to set the relation between the DEV and UAT Issues.

Let us know if you have any questions.

[sharmila patwardhan]

The solution you provided is not viable. We have 100s of projects in Jira which are using same Jira instance and workflow. Our Jira admin team can not create so many issue types based on individual project needs.
It is too much of admin stuff.

Is there a way that "Ready for UAT" can be marked in "Done category with resolution reasons. That might help the sprint to understand that the issue is closed.

In a separate Kanban board , we will track the UAT status .

[Petter Gonçalves]

Hello @sharmila patwardhan

Thank you for your details.

About this sentence:

We have 100s of projects in Jira which are using the same Jira instance and workflow. Our Jira admin team can not create so many issue types based on individual project needs.

Actually, you would need to create only two issue types, properly mapping them to separate workflows and them mapping to your projects. Anyway, I understand how cumbersome this change would be for 100 projects.

Answering your question: Yes, you can mark the "Ready for UAT" status with a valid resolution and a status in the done category at the workflow, however, this is not the way Jira was designed to work, so I must confess your reports might not work as expected with this configuration.

As I mentioned before, an issue will be considered done when you add the valid resolution and status to it, so in order to keep tracking the issue in the Kanban board after the READY FOR UAT status, you would need to reopen the issue, which might cause the first Velocity Report to display incorrect data. Basically, the results of this configuration are unknown, so you would need to test and confirm how the reports would behave in this way, but I can confirm to you it will not display the way it should.

That being said, I think the best option would be to update your projects gradually in the way I suggested in my first answer which is the way Jira is designed to work and would properly display the data you want, as explained in the documentation:

View and understand the velocity chart

Let us know if you have any other questions about the information provided.

[sharmila patwardhan]

For the Kanban board, i would just need that to move from one status to another. Do i have to still reopen it?Issue resolved, can any way be moved to closedWhat is the need for reopening issue?
Without reopening, will it still let me move from different statuses?The expected report that I need is velocity chart.

[Petter Gonçalves]

Hello @sharmila patwardhan

Yes, you should be able to move closed issues from one status to another in the Kanban board, but then the reports related to your Kanban board will not track those issues.

Basically, the need to reopen an issue would be to use the kanban reports, however, If you don't need any of the reports in the Kanban board for your UAT team, this option might work for you. 

Just make sure the estimation of those closed issues are not changed posteriorly because it can also affect your Velocity report in the scrum board.

Let us know if you have any other questions.