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

Jira Automation - Can delete issue links in one project but not another with same permissions

Maria DePasquale

I have a global automation set up. I run it as an admin user. The two projects share the same permission scheme and the admin user has administrative rights. The issue links delete just fine in one project but not the other. The automation log doesn't even show the issue link deletion to have been attempted in the project where it fails. I have attempted to move the delete issue link to various places in the automation but I shouldn't have to since the automation works just fine in one of the projects. I am running Jira Data Center. Has anyone seen this odd behavior? Shown are the automation, the results from the project where it doesn't work and the project where it does work.

Didn't work.JPG

Accepted answers

All comments

Trudy P Claspill

Hello @Maria DePasquale

Please show us the automation rule and the output from the audit log.

Maria DePasquale

Screenshots added. Thank you.

Trudy P Claspill

The absence in the first audit log of entries about deleting links suggests that the issue that triggered the rule did not have any links of the specified type.

Can you create another scenario that you would expect to fail in the same way? And show us an image of the trigger issue before the rule is run, including the Linked Issues section?

Maria DePasquale

The issue had two links, one that got created the first time and one that got created the second time. The first link did not get deleted prior to the second link being created as it should have. So, this does not suggest that there were no links but rather, something isn't working correctly. The scenario always fails in the one project but is always successful in a second project, both sharing the same permission scheme and both owned by the same administrator with full admin rights. I can run the exact same automation in the exact same way. It fails for one but not the other.

Bill Sheboy

Hi @Maria DePasquale

I notice your rule is making two edits to the issue in the same rule. When doing this, please use the Re-fetch Issue action in-between them. That will reload the updated issue data before proceeding with the second edit.

Kind regards,
Bill

Maria DePasquale

Thanks, I already tried that. Still doesn't work. It's as though the Automation doesn't recognize the link existing in one project but does for the other project. I also tried changing the link type in the automation and that didn't work and I also tried manually creating the link and letting the automation delete it. That didn't work either.

Bill Sheboy

Have you confirmed the link type is correct in your delete action? Issue links have "direction", such as "blocks" and "is blocked by", and so perhaps the type is incorrect.

Have you checked if there are any duplicate link types set up, with the same name? That might confuse the automation rule.

Next, as this is Jira Server, when was the last re-index performed?

Maria DePasquale

The link type is correct for both the add and the delete - "is child of"

Keep in mind this automation works for one project and not the other so it's not a link type mismatch/dup situation. I will inquire about the last reindexing. We upgraded in May(ish) so that may be the last time. Thank you

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-administration

jira-server

atl-gruland