Managing Request Reopenings in JSM Cloud After Resolution
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
In some scenarios a Jira Admin may not want customers to reply to a closed request after a given amount of days and would prefer them to log a new request on the portal in Jira Service Management.
A workaround for this scenario is creating an automation flow that triggers each time a customer replies to a closed work item and adds a public comment on the work item, asking them to log a new request instead if X number of days has passed since it was closed.
This article applies to Cloud only. If you are on Jira Service Management Data Center, refer to Notify Customers on Replies to Closed Issues in JSM Data Center
Solution
Limit reopening a request using Automation
Customer Notifications for 'Public comment added' is turned on
This automation relies on the customer notifications, please verify that the following is enabled:
Space Settings > Notifications > Customer Notifications, and make sure that notifications for Public comment added are enabled.
For this method, you can create a new automation using the template When a customer comments on a closed request → then reopen the request from the automation templates library. Make sure you don't have multiple Flows performing the same actions.
Add another Condition to the flow from the template to validate whether the work item was resolved within the last X days. If it doesn't match the condition, it will add a comment for the Customer, asking them to open a new request. See the steps below:
In the automation Templates tab, select When a customer comments on a closed request → then reopen the request.
Between the template Flow JQL condition and the transition action of the automation, add an IF/Else condition.
Inside the IF: matches branch, add a {{smart values}} condition with the following values:
First Value: {{now.diff(issue.resolved).days}} Condition: less than Second Value: X (maximum number of days you'd like to allow customers to reopen the request)
Drag the existing Transition work item action to nest it inside this branch.
Add an ELSE condition branch.
Inside this Else branch, add an action Add comment to work item.
Configure the message you'd like to post as a comment to prompt the customer to open a new request.
Make sure the Comment visibility is "Share with customer."
You can use smart values to dynamically update the reporter name, key, and other information in the comment.
Save the Automation Flow.
Modify the workflow to limit reopening requests
Known limitations
Transitions executed from the Jira Service Management Portal ignore validators, as stated in this documentation: Show a workflow transition in the portal. We have an ongoing Feature request to provide this functionality: JSDCLOUD-5853 - Customer Portal Does Not Display Custom Validator Error.
The method can work if the reopen transition is done by an automation rule triggered by a comment added by the customer from the JSM portal. The rule will run, but report an error due to failed validation.
This solution assumes you have a workflow that has a transition that allows your Customers to transition work items from CLOSED to OPEN. You will add a validator to this transition that allows it only if the issue was resolved within the last X days.
Go to Space Settings > Request management > Workflows.
Find the relevant workflow for the relevant work type, then click the edit workflow.
Select the relevant transition (the arrow, not the status), then click Rules > Validate Details > Add Validate Details Rule.
Click Validate a Field. Then for each selection, use the following:
Validate That Field: Compares to another date
For this field: Resolved
On Expression tab:
Ensure "Resolved" is: Later than or Same As
Expression: -14d
Configure the validator as needed (If you want to allow work items to be reopened only within 15 days from resolution, the condition would be Resolved > -14d), then click Add.
Perform steps 3-6 for all relevant transitions.
Publish the workflow.
Verification
Test reopening a resolved request both ways:
Via a customer comment on the portal within the automation's trigger scope.
Confirm the Automation-based block correctly stops reopening outside the allowed window in the portal case, since the workflow-validator method alone won't catch that path.
Directly via the agent-facing workflow transition.
Was this helpful?