Is is possible to set automatic Due Date when issue is created and can only be changed by one role?
Hi @Bunyodbek Kosimov
You can use automation to set due date during create action and you can limit Schedule issue permission to certain role to limit group of people that can edit due date.
Regards,
Seba
Hi Sebastian,
Thank you for your assistance.
Yeah, I used this option. However, what I want to do is to give exact deadline to an issue like Day and exact time.
Also is it possible to set "Due Date with Exact time" and check how much time developer spent on solving that particular issue (like it starts to count when issue status is switched to "In progress" and shows how much time he was in that status) and have options like pausing the timer (by some role) for some time and resume it or give more time to finish it. Thank you
Duedate is date type field so you cannot set date and time. If you want to this you need to use other customfield which allows date and time. To manipulate date and date/time fields using automation please check this doc.
Also is it possible to set "Due Date with Exact time" and check how much time developer spent on solving that particular issue (like it starts to count when issue status is switched to "In progress" and shows how much time he was in that status) and have options like pausing the timer (by some role) for some time and resume it or give more time to finish it.
It is possible but need extra field and some automations. My idea:
- when issue is transition to e.g. in progress you will catch date and time of this transition in date/time customfield (on workflow or by automation)
- when issue is transition to status where time should be stopped (resolved/block ststus) you catch date and time of this transition to second date/time customfield (on workflow or by automation)
- then automation rule will calculate difference between this two field and put it in 3rd field
- these steps you will be reproduce every time when time should be calculated.
Also I think you can consider SLA app to achieve this.
Thank you for your help @Sebastian Krzewiński
I guess I will consider the SLA s because using the first method requires more fields
It looks like you're new here. Sign in or register to get started.
