Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation for Jira doesn't trigger parent post function

Aleksandr Stasko (EPAM) June 2, 2020

Hello,

We are using JSU to create some post-functions like transition linked issues. Recently, we've started to use Automation for Jira for simple things like move ticket to Done when all sub-tasks in Done status. After that, we noticed that JSU post-functions stopped working.

Our workflow like this:

Create a ticket -> Create sub-tasks -> Done all sub-tasks -> Parent ticket moved to Done by Automation rule -> Here should trigger JSU post-function to change the status of issue linked to the parent ticket

If I move to Done parent ticket without Automation rule post-function works as expected.

What could I miss?

3 answers

1 accepted

0 votes
Answer accepted
Michael Nidel June 3, 2020

Hi @Aleksandr Stasko (EPAM),

I would like you to help you with this. Please open an issue at our service desk

https://servicedesk-apps.beecom.ch/servicedesk/customer/portal/3

Best regards

Michael Nidel

  

Aleksandr Stasko (EPAM) June 3, 2020

Hi @Michael Nidel

I've created a ticket as you suggested.

I will wait for response.

Regards.

Like Jack Brickey likes this
2 votes
Michael Nidel June 5, 2020

Hi @Aleksandr Stasko (EPAM),

As discussed when we resolved your use case, we proposed a JSU only solution and it worked like a charm!

To help others experiencing this problem, here’s what JSU can do from beginning to end of your specific issue:

1. JSU can transition parent of subtask when all subtasks done

Overview.jpg

2. JSU can consequently change the status of issue linked to the parent issue 

This illustration shows how the configuration looks like:

Linked Transitions.jpg

We are unsure why Automation for Jira is causing the second part of the process to halt but as we’ve both realized, JSU can do this operation from start to finish.

Feel free to contact me again if you encounter any problems.

Best,

Michael Nidel

0 votes
Jack Brickey
Community Champion
June 2, 2020

That sure is odd. My first guess would be some permission issue where JSU doesn’t recognize A4J user as being allowed to execute the PF. What about simply using A4J to achieve the whole process?

Aleksandr Stasko (EPAM) June 3, 2020

Hi Jack, thank you for your response.

I'm not sure that it's the case. I mean we don't have any specific permission configuration. All are by default. If you can provide some details on where to look, I will.

As for using A4J for the whole workflow, we have a more complicated workflow. I described the only part that doesn't work. And I'm afraid that we will run out of execution limit for A4J.

Cheers.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events