Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
bgColor#F4F5F7

Example:

Let's imagine you are assigned 3 tasks. Each will take you 3 hours, and you work 9 hours a day. You have 1 working day to complete everything.

If you pick Calculate from calendar and you finish all 3 tasks in 1 working day, the result will be as if you spent 9 hours on each activity, which equates to 27 hours for 3 tasks. That wouldn’t make any sense.

To fix this, you can enter 3h for Custom Duration and show that you've worked for 9 hours in total. This would provide a more logical result in showing how much time was spent on a jobtask, especially when getting a report.

...

Panel
bgColor#F4F5F7

Example:

Let's imagine you live in Istanbul (GMT+3). Your team in Dublin utilizes a calendar set to its time zone, which is GMT+1. When it is 3 pm in Istanbul, it is 1 pm in Dublin.

Assume you created a new issue. This issue will not start counting until the Start Date matches the time in the selected time zone. So, if the issue's Start Date is set to 9 am Dublin time, counting won't begin until 9 am Dublin time. When it is 9 am in Istanbul, you will see the SLA Panel in your issue with the Start Date and Target Date calculated according to your time zone. However, the elapsed duration won't start counting in this time perioduntil it’s 9 am in Dublin.

🤔 Are the calculations based on the assignee's or the reporter's time zone?

...