Hey,
I have a Problem while starting to work with jira and especially BigPicture, trying to illustrate Progress with a Project.
First let me explain my Problem:
We have started to upgrade our users Computers from Windows 7/8 to Windows 10. So i created issues for nearly every Departement in our Companie to Show in Detail what we have already done.
I have a Problem with tracking the Progress in each Departement. The Story Points i assigned to each issue are the numbers of Computers in that Departement. That way we can see exactly how much work there is to do for each issue. My Problem is that I want to Show Progress. Is there a way I can Show how many Computers we have already finished and hoch many are left to convert to Windows 10? So lets say there are 30 Computers in one Departement and i want to say that we have converted 10 of the them. Is there a way to say that we finished 10 of 30 Story Points?
Hope you can help with our Problem and if you can think of another way to help me, please let me know.
although this isn't really a BigGantt question, I might be able to give you some ideas. Your question is actually about how JIRA estimates and then tracks progress on an Issue. JIRA uses a field called Original Estimate, that you can configure to use either time or points. Then, you must have a way to track progress by logging work against that Issue. We use Tempo. then, in BigGantt, you have to set up a Perspective that has the progress meter on it.
I actually do not know the specifics of how to do this, but this may help
If you are trying to burn down points, I think you'll need the Original Estimate field and then a 'Time Spent' field, which would then do the math for you on how much is left?
you should post the question on the broader JIRA board, because once you get the rigging set up in JIRA, it's just a matter of how to make BigGantt display it (which is probably the easiest part).
another way to do this, to save yourself the trouble, would be to create one sub-task in each Story (one for each workstation) and then have the users mark the task done when they set up the workstation. That way you could use a BigGantt configured at the Task level to show aggregated progress. And you could set a trigger to close the parent story when all Tasks are done.
(again, a question for the JIRA board, rather than BigGantt).
I hope this helps!
Thanks a lot for your answer! The link helped me unterstand the problem and how thetracking could actually work. Thanks for that.
Unfortunatelly i don't have admin permissions to check out the Estimation configuration, so i have to work until he will be available.Â
But one more question, i have after reading the text in the link. The author talks about Sprints most of the time, but we use a canban board so we don't have any Sprints, am I right with that?
I also can't see a Original estimate field, while creating issues. Do I have to activate it somewhere in the Projects configuration?
Sorry for all those questions, but I'm still pretty new to Jira and we are just getting used to it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The board type doesn't matter. You can set the estimation style to points or hours for either board type. You will have to add the Original Estimate field to your Screen configuration, and then make sure that Screen is in the Screen Scheme for the Issue Type (if you're using Stories, Tasks, Bugs, etc. make sure it's added to all of the Issue Types you use). Again, these are great questions , but they are for the JIRA discussion, rather than BigPicture.
Your JIRA admin can help you with all of these questions as well. Good luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.