I would like for the comment field to be required whenever someone closes a ticket.

I made the 'Comment' Field Required using Behaviours in Script Runner Plugin.
So whenever i edit something it asks to put in a comment. It even works for transitions.
Isnt this a Solution ? What am i missing here ?

Thanks for everyone's feedback and votes.

We've taken a look and we've decided that we won't be implementing this feature in the near future. We will be focusing our development efforts on other work that we believe will deliver a better experience.

Please note that votes is one of the determining factors that we use to plan our roadmaps, for a full description please read our blog post: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com.

We hope you understand and appreciate our honesty on these requests.

Thanks,
Otto Ruettinger
oruettinger @ atlassian dot com

Similar to JRA-4972

The JJUPIN plugin introduces a Simple Issue Language meant to simplify your special processsing in conditions, validators or post-functions.

The next code implements the same behavior as requested by this issue.

if(not(hasInput("comment"))) 
   return false, "Comment", "A comment is required";

The return values of a validator describe:

• false: the result of the validation
• "Comment": The name of the field having validation issues
• and the message to be displayed

Here is how you create a condition, validator or post-function: http://confluence.kepler-rominfo.com/display/JJUP20/Writing+Validators%2C+Postfunctions+and+Conditions

Give it a try here: https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.jjupin
or here http://jira-plugins.kepler-rominfo.com/x/product/id/3

This is a specific example of the wider requirement represented in JRA-15297. I encourage everyone to vote on that request.

Requiring comments on all edits would be really useful. Right now, someone comes and moves my issue out of a version without any explanation. I need to fetch the guy and ask for the reason. A comment would save the time for both of us and also record the reason.

There are two issues.

One is requiring comments on transitions. There are validators that do this nicely:

http://confluence.atlassian.com/display/JIRAEXT/JIRA%2BMisc%2BWorkflow%2BExtensions

The second issue is requiring comments on all changes. That is a different kettle of fish entirely and I can't provide any pointers.

We also have a requirement to force the user to add a comment. This seems like a simple option to enable or add it to the workflow.

Quote:

One problem I have with this though - what's to stop a user just putting in "." or random junk text when a comment is mandatory?

... Regular expression validation?

This would be incredibly useful, as long as it is done in such a way that we (as in Administrators) can choose where comments are required. I have workflows where I could really use mandatory comments on some transitions, but not others.

For example, "resolve" and "close" transitions - I don't need a comment (most of the time, the user sets a resolution that says it all, or the close is just the user saying "yep, I'm happy"), but I really do need a comment on "re-open" or "cancel"

One problem I have with this though - what's to stop a user just putting in "." or random junk text when a comment is mandatory?

This feature would benefit us and allow a trail of comments through the life of the defect.

This would be useful to have.

Yes, please.

Count us too. We have several Escalation states transitioning to which without an explanation is the least wanted.

There must be an ability to use a Validator to check if Comment has been entered or not.

This would help us a lot too. Ideally I would like the option to independently make comments mandatory for edits and workflow transitions.
For example we don't normally need it for edits as only a few people have the ability to edit issues and it is usually obvious why the edit was done by looking at the change history.
With workflow transitions however, it is important that the next person in the chain knows what to do next and unfortunately marking an issue as resolved may not convey details such as whether the change has been deployed somewhere or whether the client has been informed. Forcing a comment entry would assist greatly.

We need it in our company either... Is there any workaround to force users fill in comment we can use right now?

Seems to be a duplicated by JRA-12975. If we combine the votes we would already have 18.

Just voted for this issue. This would really help our company too, as it would force users to justify / explain any changes they make to an issue.

I agree. This will be great for our company too.

I agree with Erich and Dion. Please enhance.

We have this requirements as well. This is a must have feature in controlled/audited environments. JIRA is almost there with the change history. Just need to be able to force the inclusion of a comment to describe/justify the changes that JIRA is already capturing