I'm confused. I recently updated the BP plugin to the latest version (8.44.0) in Jira DC Released on 2024-12-12. In the Gantt module, on the bottom panel "Resources", when viewing the scale with Workload details, if the Aggregation mode "Daily" is enabled, the issue list and their Workload values (that form the total figure "Total workload") are not shown Just summary information is shown in the window when you click the mouse on the cell with the number on the diagram: Effort mode: Remaining estimate Total workload: Remaining capacity: If you switch to the Aggregation mode "Weekly", the issue list is displayed correctly. Are you not aware of whether this problem is caused by the latest update or what happened?.. I remember for sure that before viewing "Workload details" worked correctly and I saw the issue list. how does it work for you now? * when hovering the mouse over a cell with a number on the scale. Moreover, in the "Resources" module itself and in the "Daily" mode, the "Workload details" information is displayed correctly
I only have a cloud instance available to me right now, and it's looking fine over there. It may be a bug in your DC version. Consider raising a ticket to appfire for this.
Hello, is it possible to fix the following in BigPicture: There is a task and it is scheduled for today, its original estimate = 3 hours. Effort Mode = original estimate Why, when changing the status of this task to "done", its original estimate (3h) continues to affect Workload (8h). It is logical that the task is completed and should no longer affect Remaining capacity. Yes, I understand that if I use Effort Mode = Remaining estimate and specify Logged Time, then I will see the load correctly. But I do not want to engage in excessive micromanagement. It would be enough for me to use Effort Mode = original estimate. Is there a solution to this annoying misunderstanding when changing the status to Done?
Hi. There is nothing wrong with the scenario you've described. Original Estimate effort mode is a simplified view where the workload is only calculated based on the value coming from this one field only. If it'd stop calculating hours after the tasks are done, then you'd stop seeing all the historical data.
@@geniusgecko-project-management hi, thanks for the answer. I tried to use the effort mode "Remaining estimate", yes, this mode shows the Workload more accurately, provided that the issue with the status "Done" has the value "Remaining estimate" = 0. This is achieved if I specify Logged Time, but in my case I do not want to waste time maintaining Logged Time. I thought that it might be possible to simply make a condition through automation in Jira: when switching the issue status - "Done" - automatically make Remaining estimate" = 0
@@jhondavis1264 If you do this automation, then the data for the past (earlier than today) will show zero workload, because in this effort mode it's coming from logged work (and you won't have this). That's why I'm not sure if this solves the use case. I have a suggestion. I'd like to treat this as a learning opportunity for a member of our team. If you'll send me an email to info@geniusgecko.com, we'll set up a meeting to discuss this online. This will be better than exchanging comments here. Drop us a note if you want to do this :)
I'm confused. I recently updated the BP plugin to the latest version (8.44.0) in Jira DC
Released on 2024-12-12.
In the Gantt module, on the bottom panel "Resources", when viewing the scale with Workload details, if the Aggregation mode "Daily" is enabled, the issue list and their Workload values (that form the total figure "Total workload") are not shown
Just summary information is shown in the window when you click the mouse on the cell with the number on the diagram:
Effort mode:
Remaining estimate
Total workload:
Remaining capacity:
If you switch to the Aggregation mode "Weekly", the issue list is displayed correctly.
Are you not aware of whether this problem is caused by the latest update or what happened?.. I remember for sure that before viewing "Workload details" worked correctly and I saw the issue list.
how does it work for you now?
* when hovering the mouse over a cell with a number on the scale.
Moreover, in the "Resources" module itself and in the "Daily" mode, the "Workload details" information is displayed correctly
I only have a cloud instance available to me right now, and it's looking fine over there. It may be a bug in your DC version. Consider raising a ticket to appfire for this.
Hello, is it possible to fix the following in BigPicture:
There is a task and it is scheduled for today, its original estimate = 3 hours.
Effort Mode = original estimate
Why, when changing the status of this task to "done", its original estimate (3h) continues to affect Workload (8h).
It is logical that the task is completed and should no longer affect Remaining capacity.
Yes, I understand that if I use Effort Mode = Remaining estimate
and specify Logged Time, then I will see the load correctly. But I do not want to engage in excessive micromanagement.
It would be enough for me to use Effort Mode = original estimate.
Is there a solution to this annoying misunderstanding when changing the status to Done?
Hi. There is nothing wrong with the scenario you've described. Original Estimate effort mode is a simplified view where the workload is only calculated based on the value coming from this one field only. If it'd stop calculating hours after the tasks are done, then you'd stop seeing all the historical data.
@@geniusgecko-project-management
hi, thanks for the answer.
I tried to use the effort mode "Remaining estimate", yes, this mode shows the Workload more accurately, provided that the issue with the status "Done" has the value "Remaining estimate" = 0.
This is achieved if I specify Logged Time, but in my case I do not want to waste time maintaining Logged Time. I thought that it might be possible to simply make a condition through automation in Jira: when switching the issue status - "Done" - automatically make Remaining estimate" = 0
@@jhondavis1264 If you do this automation, then the data for the past (earlier than today) will show zero workload, because in this effort mode it's coming from logged work (and you won't have this). That's why I'm not sure if this solves the use case. I have a suggestion. I'd like to treat this as a learning opportunity for a member of our team. If you'll send me an email to info@geniusgecko.com, we'll set up a meeting to discuss this online. This will be better than exchanging comments here. Drop us a note if you want to do this :)