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

Auto Close tickets using built in Escalation Service

RahulG

Hi,

I am trying to use the built in Escalation service to auto close tickets (in my case, from status: "Resolved Awaiting Verification" to status: "Close"). I have 20+ workflows with this exact same transition pattern, but of course, different transition IDs Do I have to create one escalation service per workflow? That would seems silly. Is there a way to write ONE generic escalation service will work for all of my workflows? Jelly script was able to do it the generic way. Could you please help me regarding this @Jamie Echlin [Adaptavist]

Thanks!

Accepted answers

JamieA

If the workflow action IDs are the same you can use the same escalation service. I think the question is more why do you want 50 different workflows.

Anyway, say you have 50 genuinely different workflows, you can just write your own service rather than using the escalation service, which is just a shortcut.

Anything you can do in jelly you can do in groovy. There is a complete example here for looking up the action ID by name: https://scriptrunner.adaptavist.com/latest/jira/recipes/jelly-migration.html#_in_code

All comments

unknown

Why did you have to create multiple transitions of "Close"? You can just 're-use' an original every time you create a new workflow. One of the downsides with this is that whatever you properties/validators/post-functions/conditions in Close (1), it will not be inherited when you create a new Close (2). Or you design it this way?

As for the question itself, I think you can "suggest" a feature for it against the vendor (Adaptavist)

RahulG

I am not aware of a way to " Re-use" any Transition among different workflows. what did you mean by "Re-use"? Yes, we are designed in a way where we have multiple close transitions, they are in different workflows, therefore they have different transition IDs. Is there any specific way which exactly do as same as jelly script ?

unknown

https://confluence.atlassian.com/display/JIRA043/Configuring+Workflow#ConfiguringWorkflow-Using'commontransitions';

Royce Wong

I am using JIRA 6.2.2. I have the same problem. I read https://confluence.atlassian.com/display/JIRA043/Configuring+Workflow#ConfiguringWorkflow-Using%27commontransitions, and I am aware you can share a transition in one single workflow, but there is no way to share a transition between different workflows. Am I correct? I have 50+ workflows, each different but with exact steps and transition to close issues. It doesn't look like Script Runner's built-in Escalation Service can handle all in a generic fashion (like Jelly script can). I will have to write a custom groovy script to do the generic way, correct?

JamieA

If the workflow action IDs are the same you can use the same escalation service. I think the question is more why do you want 50 different workflows.

Anyway, say you have 50 genuinely different workflows, you can just write your own service rather than using the escalation service, which is just a shortcut.

RahulG

Thank You Jamie.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration