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; } } }

Autoclose parent ticket in PRODSEC based on status of linked tickets

Anusha Ramesh_uqjz14

In JIRA, is there a function that allows for automating closure of linked tickets? If I have a ticket (ticket A) that is linked to another in a different queue (ticket , either as dependent on or related to, and the other team closes ticket B, can that closure trigger ticket A to be auto-closed? Ideally with notification to owner and watchers of ticket A.

In the case of multiple links in a single ticket, ideally the logic would be that the project ticket would auto-close after all of the linked tickets are closed

Accepted answers

Daniel Ebers

Hi Anusha,

welcome to Atlassian Community!

You could do something like this for example with Script Runner (Script Jobs / Escalation Service).

I used to implement this in the past for a use case that reads:

- an issue in project ACCOUNT
- that is currently in status "on hold"
- should be closed (you can define this in the Script Job section as well)
- as soon the/all linked issue(s) is/are closed

project = ACCOUNT AND status = "On Hold" AND issueFunction in linkedIssuesOf("status = Closed")

Please note this depends on if you already have Apps that are capable of fulfilling this requirement. In the example Script Runner was used but there are probably other Apps from Marketplace which are also suitable.
Please note: the App in question needs extra payment.

There is also Automation from Atlassian - but this is nowaways extremely popular with Cloud.
You mentioned server why I wanted to share the approach using Script Runner.

Cheers,
Daniel

Anusha Ramesh_uqjz14

Hi Daniel,

Thanks much for your response, we have scriptrunner and I will be grateful if you could help me with a script to achieve auto close particular issue type only.

Also, at times there may be more than 1 linked 'depends on'.

Please help. Appreciate your heads-up here.

Thanks

All comments

Daniel Ebers

Hi Anusha,

welcome to Atlassian Community!

You could do something like this for example with Script Runner (Script Jobs / Escalation Service).

I used to implement this in the past for a use case that reads:

- an issue in project ACCOUNT
- that is currently in status "on hold"
- should be closed (you can define this in the Script Job section as well)
- as soon the/all linked issue(s) is/are closed

project = ACCOUNT AND status = "On Hold" AND issueFunction in linkedIssuesOf("status = Closed")

There is also Automation from Atlassian - but this is nowaways extremely popular with Cloud.
You mentioned server why I wanted to share the approach using Script Runner.

Cheers,
Daniel

Anusha Ramesh_uqjz14

Hi Daniel,

Thanks much for your response, we have scriptrunner and I will be grateful if you could help me with a script to achieve auto close particular issue type only.

Also, at times there may be more than 1 linked 'depends on'.

Please help. Appreciate your heads-up here.

Thanks

Daniel Ebers

For a single issue type you just need to adapt the JQL like "project = TEST AND issuetype = Bug" for example.

It is not really a script needed there, you can use Script Runner (Script Jobs / Escalation Service).

https://scriptrunner.adaptavist.com/6.14.0/jira/ScriptJobs.html
https://scriptrunner.adaptavist.com/6.14.0/jira/escalation-service.html

Anusha Ramesh_uqjz14

Yes Daniel, But escalation service help on auto close with the status of an issue.

Does this service help us to have an issue auto closed when linked issue(s) are closed with 'depends on' link type ? If yes could you please route me.

Thanks

Daniel Ebers

Yes, this is is already basically covered by the following part of JQL I posted above:

[..snip..] issueFunction in linkedIssuesOf("status = Closed")

and can be extended like this is you wish

[..snap..] issueFunction in linkedIssuesOf("status = Closed", "depends on")

What is absolutely true for this powerful implementation - a hour or two of testing is needed for sure.
Here is the extensive documentation for all further fine tuning
https://scriptrunner.adaptavist.com/6.14.0/jira/jql-functions.html

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