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

Closing issue on customer portal with comment, Reopen the issue - in clash with reopen automation

Vasumathi Jayakumar_hf37pn

As per the show transitions on the customer portal, we have added the "Resolve" transition to the portal. So the customer can close his/her own issue.

We also have an automation rule to reopen a closed ticket, when only a customer comments in it.

The problem now we have is, when the customer via portal resolves the issue with a comment in the resolveissue dialog box, the issues is closed but again reopened because of the automation rule.

How to handle this, any condition that can be added to the rule?

Accepted answers

All comments

Nicolas Seronvalle

In the automation rule setting, what does your condition (IF) looks like?

René Schabacker

We're facing the same issue. "WHEN" says "Comment is added to an issue", "IF" says "status = "Waiting for Customer to Close"" AND "user is not an agent".

It is meant to trigger reopening if a customer adds a comment after we resolved the issue. But it also triggers when the issue was transitioned to the status "Waiting for Customer to Close" by the customer and the portal requesting a comment. So the customer resolves the issue and adding a comment at the same time. But JIRA seems to do two separate steps - one is transitioning and the other one is commenting afterwards. Hence issue is resolved an reopend again by automation rule.

Is there anything we can do?

Brian B.

Any luck solving this? We just added the Resolve transition to the portal and now are seeing items get reopened when customer puts a friendly comment in such as "It works now, thanks!", etc. I suppose if there was a way to adjust the automation rule to say if customer is resolving and not agent.

Ryan Stafford

I believe this is caused by the order of the "Essential Post Functions".

Essential post functions
Every Jira transition has the following essential post functions, which are performed in this order:
Set issue status to the linked status of the destination workflow status.
Add a comment to an issue if one is entered during a transition.
Update change history for an issue and store the issue in the database.
Reindex an issue to keep indices in sync with the database.
Fire an event that can be processed by the listeners.
These essential post functions cannot be deleted from a transition or reordered. However, you can insert other (optional) post functions between them.

I assume if steps 1 and 2 were switched this wouldn't happen. Unfortunately they can't be reordered. Maybe setting the issue status again after comment would work.

unknown

I can't seem to find it, but I believe there is an issue raised for this we can vote on

Nicolas Seronvalle

Hi,

In the "If" of your automation rule do you use the "Comment is the primary action" condition?

See https://jira.atlassian.com/browse/JSDSERVER-4348 and the documentation about it https://confluence.atlassian.com/servicedeskcloud/automating-your-service-desk-732528900.html

Vasumathi Jayakumar_hf37pn

Hi,

Yes, if we set comment as a primary action re-open rule works fine.

Thanks

Jeffrey Bistrong

Following as this is happening to me as well, it seems in jira cloud you can't re order all of the post functions

Chrisjir Parkin

Disclaimer: I haven't tested this and I don't know if it applies to this problem, however ...

...in JSD automation, there's a checkbox for whether a rule can be triggered by other rules. Could it be that unchecking that box would disconnect the close-comment-reopen cycle? Just a thought.

Rule triggered by other rule 2020-11-02.jpg

Petr AST

@Jeffrey Bistrong

Hello. Did you manage to solve this issue?

Jamie Schwartz

This seems to be the answer but still only works with Legacy Automation for Jira Service Management. It will NOT work in the new automation since there are still several missing attributes that legacy automation supports such as "primary action is comment." Once I setup legacy automation this worked perfectly fine as described here.

Petr AST

@Jamie Schwartz You can add a JQL with a resolution time of less than -1 minute

resolutionDate <= -1m

It helped me.

Jeffrey Bistrong

I did by using the JQL resolutiondate <=-1m

Seems like this is a known issue: https://community.atlassian.com/t5/Jira-Service-Management/how-to-check-that-a-comment-is-a-quot-primary-action-quot-using/qaq-p/1709376?utm_source=atlcomm&utm_medium=email&utm_campaign=accept_as_solution_reminder&utm_content=topic

Petr AST

Hi @Jeffrey Bistrong

True:) Thanks anyway) I found the resolution that day

https://community.atlassian.com/t5/Jira-Service-Management/Closing-issue-on-customer-portal-with-comment-Reopen-the-issue/qaq-p/1659018#M75678

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk

jira-service-desk-cloud

jira-administration

customer-portal