nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tracking SLA of tasks which have dependencies on other tasks

Zeki Can KARATAŞ

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?

Thanks.

Accepted answers

Alex Laycy_dvwa4f

Hi Zeki,

Could you post a screenshot of an example issue?

Are you creating an issue within service desk, and then creating sub-tasks within it?

- Alex

All comments

Alex Laycy_dvwa4f

Hi Zeki,

Could you post a screenshot of an example issue?

Are you creating an issue within service desk, and then creating sub-tasks within it?

- Alex

Zeki Can KARATAŞ

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.

Alex Laycy_dvwa4f

Hi Zeki,

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)

- Alex

Zeki Can KARATAŞ

yes we are using SLA tracking but we cannat manage to connect a tasks start of SLA to another one's closure. can we do this with SLA plug in?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server