I differenciate between effort and duration of an issue. The effort is reflected by the JIRA field "original effort" or as aggregation of already logged work and remaining estimated effort. The duration is delimited by planned start and planned end date. For example, if you boss decides to deliver an issue one day earlier to the customer, this has an impact on your planning but not on the estimated effort if the scope is unchanged. Same in case of a change of estimated effort: this may have an impact on the duration but not necessaryly. If you habe less effort, you can keep the original plan end date and regard the difference as buffer to reduce risks or you work on other issues in parallel or ... If the total amount of effort increases, you also have to decide what to do: you can keep the planned end date and split that task into multiple (sub-)tasks assigned to different team members to match the communicated goal or the assignees have to work longer per day or during the weekend or you deliver later by shifting the planned end date (offten, you have restriction and cannot always move the end date into the future: e.g. deliver Christmas trees in January is not an option). In all cases, it is a decision of the project manager or the agile team depending on your local organisation but not an automatic action of a computer program conceptionally. Instead, it is important to assist any decider and focus on such situations (indicated by yellow/red coloring). If you decide to adjust the planned end, then reflect this by explicitely moving the end of the Gantt bar via drag'n drop to the new date. All depending issues as well as subtasks are automatically adjusted accordingly, taken global calender as well as project calender and assignees' calenders into account.
Manage space
Manage content
Integrations