We would really appreciate this feature so Approvers can comment on why they do not approve a request.

not just add an option in JSD or Workflow settings that allows administrator to make this comment field mandatory, while performing a webhook to another platform (eg ServiceNOW), the field is using a different payload and the comments will not be reflected in ServiceNOW.

This results in agents in the other platform unable to view the comments and reason the status was transited.

Thus would appreciate this feature can be fixed as well.

Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

+1

+1

+1

+1

Please add this feature.

Thanks in advance!

+1

+1

Back for my annual check in! I have never dealt with approval workflow that didn't require a comment. A very crucial feature that was implemented in data server a year ago we are still waiting for.

@Atlassian

This is a necessary feature. If an approver doesn't add a comment in the portal, then we won't know why the request was declined.

I will post no irony, yet this would be a very helpful functionality indeed, which we don't have.

Now, to simply implement the elementary behaviour "force customer to justify his actions when pressing approve or escalate", I have to pervert with creating forms on transition, putting the task into some auxiliary status and allow actors to transition it to the desired state only by submitting this form.

Weird.

Maybe I've missed something? But, considering this thread is still alive and hot, I guess I have not.

Only 7 years ticket? Then we need to wait for at least another 8 years before Atlassian takes it into consideration. They should raise the license cost, to hire more people, then we may get down to only 4 additional years
</sarcasm>

Merry Christmas to everyone and I wish us all that Atlassian has many New Year's resolutions - e.g. to solve this issue!

a very important function. my company decided against Jira for that particular reason. (having an extra paid add-on would have been expensive)

Please introduce this feature! 

We want to make the escalate option available in the customer portal, but the comment field has to be mandatory to prevent unnecessary usage of this option. Why is there still no response from Jira on this issue?

This request is very important for the companies, all competitors have this feature enabled, and here it's been available for over 6 years.
As I'm assessing Jira's usage in our company and other group companies, this seems like a critical point in the decision-making process that weighs against the tool.

Dear Sushant,
do you have any news for us? When will it be ready for release?
BR Toby

Sad too see so many 'obvious' features unavailable

I was on the point to implement the 'Approval' functionallity today but it has been rejected simply because of this.

It seems very logic to give the opportunity to the approver to add a comment when he rejects a request...  to inform the requester why it has been rejected.

Now, you reject the issue & case is closed.   Really frustrating for the requester...

This would be a very helpful feature for my organisation.

Is there any update on this request?!? 

Also allow us to disable the comment completely 

We need this asap!!

Any Update?

We would like to use this functionality to request a reason for ticket escalation.  Please implement!!!

https://getsupport.atlassian.com/browse/JST-821852

+1

We need this feature to handle our support in a orderly manner, upvote. 

We need to track rejection reasons as a part of our data governance on approving/rejecting Change tickets. Is there a suggested workaround to be able to mandate this?

In my workflows I cannot force a comment with a rejection reason, which in effect manifests itself in the lack of justification for the rejection decision. THIS is very bad, it makes your day-to-day work difficult.

My team has this same problem. We have a work-around with Automation, but can only add a comment after all approvals have been completed. 

Sometimes requests require multiple approvals. Jira is not able to put a comment/record entry showing what exact time each person approved the request. This is a problem because when a request gets denied the ticket does not show which of multiple approving people did the denial or even which had already approved or were still not having taken any action yet.