Although you request is not totally compliant with Scrum principles, it does make sense, actually.
JIRA PDF View Plugin can be a tool to generate these and other custom reports from JIRA issues. The plugin is shipped with a simple Burn Down Chart template, that you could utilize, either as is or as starting point for customization.
It takes the input list of issues and transforms the data to the agile report below (see PDF). Using this, all you have to do is setting up a filter that returns the issues for that given person and then export the result set.
(In case it is cumbersome to set up a separate filter for each project member, the plugin supports scripting! This allows you to implement any simple or complicated logic during rendering your PDF document.)
We are currently reviewing the free version of your app. The one issue that we have is reporting on individual velocity. In our workflow, issues progress through our workflow and assigned to a different team member. It seems that your app is hard coded to only look at the original ticket assignee and not the reassignment for velocity. Is this correct? Or am I missing something on the settings? Thanks so much for your help.
When report is generated it looks at the current/latest assignee, not the value of assignee it was previous set. Please contact me at email@example.com for further support.
By definition in Scrum the velocity is a metric for the productivity of the team during a Sprint, it s not intented to monitor a single member work.
Same thing for the Burndown Chart. Using the Burn Down, the team can see if they are likely to acheive the Sprint Goal. If not, they can adapt and re-organized their work in order to make it.
What is exactly the need you have ?
I know the defeinitions given in Scrum, but that's not what we are using. We augmented it by introducing some practices for multi-project management.
Our team members work across several projects with different percentage over sprints. Some tasks can be performed only by some team members. This means that I need to monitor and limit amount of work assigned to each team member, other than the total amount of story points for a sprint.
In GreenHopper, it is not possible to put constraints on swimlanes, so I wanted to do it manually, by checking the amount of work assigned to a team member in a burndown chart.
It is odd that one of the main principles of scrum is people before processes yet each time there is a suggestion to improve process or add features to help people, this is mostly met by a stern defending of the process. I have seen this recurring on most suggestions to features. Odd. "By definition", "non compliant to SCRUM principles" and so forth.
We want this functionality to help us to see how many story points individual team members are usually completing in order to help us reduce overscheduling for those team members in the future.
That seems to me like a valid use case even for traditional SCRUM...
I'm also looking to see total points assigned and total points completed, per user for past sprints. Otherwise how do we get a feel for points per person and adjust the sprint plan when someone is away?
Viewing individual velocity will be super useful metrics to help team members to adjust their commitments. I noticed some of team members tend to overestimate tasks and and that report will help to give proper feedback to the team members.
Introduction Many users have difficulty in the initial phase of using Portfolio for Jira. They try to start quickly, in connection with which arise many questions and difficulties and as a result th...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events