JIRA Work hours association with WorklogPro and BigPicture App

[Vinay Poosa]

Hi,

Can someone help me understand if there is any association between JIRA work hours (Time Tracking) with BigPicture or its Workload plan.

I'm using WorklogPro for tracking the user worklogs at the same time I use BigPicture for resource capacity planning. Now the concern is in BigPicture I have configured Workload plan as 6h day to have my users do productive works and remaining 2h I leave it up to them for any non-productive works. So for my productive capacity planning I do for total 6h.

When it comes to logging works in JIRA WorklogPRo all the users are expected to log total 8h so in Time Tracking under Issue Features, I have configured the work hours as 8h for weekdays and 0h for weekends. I also have configured missing worklog reminders where users who have not logged less than 8h will get auto email from JIRA itself. In order for reminder to show 8h required I need to configure Work hours(Time Tracking) under Issue Features as 8h only.

Appreciate any help on this. Thanks in advance.

[Anna-BigPicture]

Hi @Vinay Poosa

There is definitely an association between Jira Time Tracking and BigPicture Workload Plan, and it’s reflected in the Resource module. The availability of a resource is derived from the Workload plans and is the basis to determine other crucial data used in Resource Management.

In your case, the base Capacity is 6 hours per day. BigPicture will not take into account the workload plan defined in 3rd party plugins. 

BigPicture calculates a resource's Workload by summing up all estimates of the assigned tasks and Remaining Capacity based on rule Capacity - Workload.

You can show the resource workload using three different modes:

• Original estimate mode - use this mode to show planned workload versus the resource capacity.
• Remaining estimate mode - use this mode to show workload history (Spent time), and the remaining workload versus the resource capacity.
• Story points mode - use this mode to show the planned workload versus resource capacity expressed in Story Points.

As you can see, the Workload Plan defined in BigPicture in conjunction with Time Tracking data gives you a big picture of our resources which leads to effective resource allocation.
Data are color-coded what helps in the quick identification of both overallocation and underallocation.

• Less than 75% of the capacity the bar will change Green color (under-allocation)
• Between 75% and 100% of the capacity, the bar will change to Orange color (moderate allocation)
• Over 100% the bar will change to Red color (overallocation)

I think it’s worth mentioning that you can auto-schedule task duration based on Time Tracking data mapping End/Start Date to time estimate fields (Original estimate or Time spent + Remaining estimate). However please note that synchronizing Start/End Date to Time spent + Remaining estimate will reflect log work from Jira what in your case means 8 hours.

Let me know if you need more info.

Best,
Anna