We have tasks which have dependencies and need to track sla for each task seperately. to make it clear; the counter for task_1 started at 03.12.2019 and due is 09.12.2019. task_2 is the consecutive task which has dependency to task_1 and so the planned start date is 09.12.2019 and due date is 11.12.2019. Both tasks has opened at the beginning. Lets assume task_1 has been finished at 07.12.2019 (before due date, in a shorter period than SLA). we need to start the counter for task_2 rather than starting at 09.12.2019 and counting 2 days (till 11.12.2019). To sum up, we need to update the start date and SLA calculation based on the closure of the predecessor.
How can we manage this issue?
Hi, our jira version is given below.
on the top, sample tasks are given. you can assume that YEK-127 is predecessor of 128. create date of both tasks are 11.11.19. due of 128 is 13.11 and due of 127 is 24.12. task no 128 has closed at 18.11.2019, 5 days after than SLA. so we want to update the start date, SLA calculation and new due date of 127 (beacuse of the delay of 128). we need this to be done by Jira automatically rather than manuel update process.
we do not want to do it manually because we have more than 100 tasks, and dependencies are complex.
by the way, we can use sub-tasks rather than tasks if it is more convenient to solve.
Are you doing anything to track SLA's at the moment? (such as using the SLA tracking capability within JIRA service desk)
You may need to use an SLA plugin from the marketplace (example) and then use a JQL query to define the SLA via linked issues.
If you create an appropriate new linked issue type then you could base your JQL on this, for use within any SLA counting.
The appropriate JQL may then be something along the lines of the following;
Project = KYRC and issueLinkType in (dependent)
I'm one of the folks behind Snapbytes, and I'm answering as the product owner of Time to SLA app.
Actually you can't bind related issue's date field but you can automate the process.
If you define an SLA starting with Date field and update this field with the related issue you will be able to see accurate SLA data.
Our team would love to help if you raise a support ticket here.
Hello @Tuncay Senturk _Snapbytes_ ,
I am one of the colleagues of Zeki and I work in product management department. Our primary purpose by using Jira platform is to create Projects as product development journey and Issues under the same Project to address the related parallel and series of tasks inside the project.
We are working with several projects simultaneously and some tasks are, like Zeki mentioned, predecessors with each other and the next task could not be started until the previous one is finished. While working with several projects at the same time, updating start and due dates of Project and other related issues in the same Project is painful for us.
At this point, we are seeking for an automated and flexible process solution to update start and due dates and eager to purchase if any plugins that are provided by Jira.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event