We have tasks that are estimated to take less than a day, for example 4 hours. 2 such tasks can fit in a single day work, but they are presented in the GUI is taking a full day each and we cannot shorten them. They automatically pop to take a full day
Thank you for your question.
Even though BigPicture has a very broad range of functionalities when it comes to 'Resources' management, it still faces some technical limitations which our dev team is trying to surmount. While looking for the best possible resolution, I believe the feature which we are planning to release in the near future and which will provide a resolution to these limitations and to the problem which you are facing, is the 'Hour Contouring'.
The feature will expand our 'Resources' module with following capabilities:
You may find more information about the 'Hour Contouring' by referring to the following backlog ticket in our Jira: https://softwareplant.com/jira/browse/BIGPICTURE-2940 (please make sure to open it in your browser's 'Incognito Mode'). Beside the detailed description with examples, you may find the video on how the feature will work.
Please let me know if there's anything else I could help you with.
Piotrek of SoftwarePlant Support Team
@amirixdid you ever find a good way to solve this issue? (:
We have more than 4000 tasks - many less than a standard JIRA day. This will show the overall schedule to be completely wrong as each small task will take up a full day.
A duration of one month is shown in the schedule to take three months instead. This is completely impossible to plan with and completely defies the purpose of a gantt planning tool!
I am interested in knowing the real date the program and its milestones shall end. Currently, this small example shows that the tasks will take 2 calendar days (as they depend on each other), where the truth is that both will end in the same day.
(Resource allocation as I saw as available in other screen, though I would be happy to clearly see over-allocation also on the Gantt itself)
but WHY do you want to do this?
if you are only interested in showing on what day the task will complete, then it doesn't matter if it's done at 10am , 2pm, or 5pm.
if you want 2 tasks to end on the same day then use the end to end link, or no link at all.
the only reason to know that a task takes < 1 day is to properly represent the resource consumption
I'm so sorry, I think I must be missing part of the problem here.
are you letting BG derive the end date based on resource availability plus the level of effort (in jira, the original estimate field)? if not, then just set the end date absolutely and set the task type to 'manual' or 'lock'.
Imagine that I had 4 tasks in my program, each estimated to take a full day. depending on each other. i.e., end-to-start relation.
Along the way it was discovered that they will take only half a day each. I update the estimation in the JIRA issue.
but now my program is showed to take more time than it really does. You can magnify this problem depending of the size of the project.
Coming from MS project, successors and predecessors is the correct way to link tasks. this feature exists also in BigPicture. Not using it means that my program is build on the wrong skeleton and is not flexible to changes (since I will need to manually examine each changed task, and manually play with links to correct the problem)
are you more interested in knowing the date (in absolute terms) that the task will be completed by? or are you more interested in knowing an allocated resource is available for 4 more hours?
a task, regardless if it takes 2 , 4 , or 8 hrs still ends up being done at the end of the day.
so what are you trying to show? the day it will be done?
Calling all collaborators and Confluence users! Our Appy Hours event on September 29th features 4 presenters demoing functionality to superpower Confluence. Don't miss learning about these apps i...