Add progress bar to track User story/Bug/Task inside ticket n display it at scrum board per ticket

Hi there,

I want to know if we can add Percentage bar inside ticket which can be displayed at Ticket level on scrum board.

There was discussion on https://community.atlassian.com/t5/Jira-questions/Progress-field/qaq-p/410394 but seems to have no mature end.

 

Reason I want to have progress bar in percentage is to know how much amount of work in pending on that particular ticket. Just at high level for management purpose so that I dont have to re-do it in excel and keep on asking developers again and again.

3 answers

Hi,

As far as I know you can add the original and remaining estimate, but not a percentage bar. 

However there are some reports that may help you. You could check the "Time tracking report" or the "Version workload report" (some documentation: https://confluence.atlassian.com/jirasoftwarecloud/reporting-764478415.html ).

To have a more high level view you can also have a look at the gadgets on the dashboard , "Jira Roadmap" for instance.

But it also depends on what you want to show to the management, is it about a print, a version or some issues in particular?

0 votes

Off the shelf, there's no percentage bar, but there are add-ons that can provide them.

The reason there was no mature end to the previous discussion was that no-one would answer the question "what progress are you measuring?" with anything useful.  I don't think you have that problem, as you've suggested you're looking at estimates and time logged.

Hi Nic,

Use of JIRA is now wide and not only to track software development, but also other activities.

E.g. Technical Task stories, this stories may need Progress Bar to track how many percent of work is done at higher level. And this cannot be achieved by Estimated Time and Remaining Time.

There are task that are created at the start of the sprint and they last almost  couple of sprints. Just in order to know how much work has been done under those technical task tickets, it would be good to have something like progress bar with an option to select how much is completed i.e 10,20 or 60 % which reflects on on ticket at high level as progress bar. I hope it makes sense.

Percentage of what?  What are you measuring when you say "progress"?

Percentage of work done to complete the task. To measure progress in other words. Say if task has 3 items, 1. Create schema, 2. Create tables and 3. Upload data.

1. Create Schema is done = 33.33%

2. Create Table is done = 33.33%

3. Upload data = Business has still not provided list of data to be uploaded, therefore = 33.33% is still pending.

Total progress on ticket = 66.66%  which can be shown as progress bar and viewed at scrum level.

So progress here is "Number of sub tasks complete / total number of sub-tasks".  That should be quite easy to code for.

Yup, "Number of sub tasks complete / total number of sub-tasks"

But in this case Sub Tasks are not created outside the ticket. Kind of Checklist option. If we have 4 items they get divided into 25% or division happens on number of sub items we have created. Do you mean by coding internally as a JIRA admin?

Um, I don't quite see that - you say they're not sub-tasks, but then they are sub items - which is a synonym for "sub tasks".

Yes, you need code to do this.  I don't know of any apps in the marketplace that will do this for you, but I would take a look before diving into code.

0 votes
Saâd DIF I'm New Here Nov 15, 2018

Hello,

We tried to do the same thing but we didn't find an easy way to do so.

 

We managed to "hack" the "Log Work" feature to use the "time spent / time remaining" in order to display a progress bar under the cars in our board.

 

The "trick" here is to log a first time the time spent as the ratio of the work done and the remaining time as the ratio of work to do.

For example, if you first log 20h spent and 80h remaining estimated the progress will be 20% (20h/100h).

After that, you can log another 40h to have a progress of 60%. And then add 60h to be at 100%.

 

This is a feature used in a completely other way it was build for but it works.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,637 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you