Is it possible to disable comments for a particular issue type?

I wish to disable the comments for a particular issue type. In effect, for a given issue type we are hoping to fully disable commenting, either at transition time or on the view/edit screens.

I can't disable it via Field Configuration as there is no option to, and Screens never have comments showing up.

I know I can do it via permissions on workflow transitions, but I'm looking to disable it entirely.

Does anyone know of a workaround for this? 

8 answers

1 accepted


Try Script runner plugin

There tou can add a behavior for fields in projects/issue types/other conditions

Then just deny writing comments for your issue type


I'm looking into this approach. I presume you're talking about a Field Validator. Unfortunately it appears to not be working in ScriptRunner. I've got a support call logged with them.

@Eban Tomlinson No, he's referring to the Behaviors portion of the ScriptRunner plugin. The problem with using a Validator is that it'll only be used (to...uh...validate) as part of a workflow transition - it validates the data entered by the user on the transition form. No use for other places you can edit. I'm looking into a routine I wrote a while back that I used to control field changes via a Script Listener but it's taking a bit to find the correct part. -wc

Ahhh. Okay, I've got it now. I'm going down this path, and I'll update when/if it works! Thanks William!

This worked like a charm! Thanks Stas!

1 votes
Pedro Cora Atlassian Team Jun 03, 2015

My suggestion would be to add the workflow property to disallow comments on all transitions. But I know that it's kinda cumbersome..

That wouldn't disallow comments on the view/edit screens though, which is also part of the request :(

I would see if you can hide the comment field in a field config and then setup a field config scheme assiging that field config to the 'commentless' issue type you want to use. I've never done that, and not sure if it'll do what you want, but in theory it should work, maybe.

Sorry for my lack of confidence here, trying to leave answers space but it keeps pulling me back in.....


No worries, I appreciate the response. In this case there is no option to disable comments via Field Configs or Schemes. It was one of the first places I went because like you it seemed like it should be possible. Sadly, it's not :(

Ok, another thought - throw a field on the issue type create/edit/view screens saying any comment added will be removed and then write a groovy listener (as with other suggestions, utilize Jamie Echlin's ScriptRunner plugin) that looks at the issue updates in the event object and removes any comment updates. I think you could just listen for 'issue commented' and strip it out there but you might need to listen for every event type. -wc

A good thought, but untenable for our current install I'm afraid as our users would just ignore it and do it anyways. I'll likely tackle this problem with training at this point.

Sorry I was unclear - I thought you'd throw the message up on the form to make users aware of what will happen to their comment if they add one (that you have automation that'll delete it). The best solution though is to just hide the damn comment field entirely if a condition is met. There's a post on someone's fail trying to do just that:

@Eban Tomlinson

adding another answer - I think this is almost there or is there for non-service-desk enabled projects.

If you look at the screenshot you see the behavior I created that removed the comment field from every place but the browse issue form - but I think that's because of service desk.

It was extremely impressive to see it work w/o but 3 lines of code which came from the in-page doc. Friggin Jamie man, his plugin totally rocks


0 votes
Joe Pitt Community Champion Jun 03, 2015

If the project only has that issue type you can remove everyone's permission to comment. However, permissions are at the project level, not the issue type level.

A viable option, but not in this case as I have other issue types in this project. Thanks though!

Hi Eban,

                I would say try Behaviours Add On which comes with Script Runner Plugin and Add behaviours for issue types as said by Stas

Good Luck!!


Chander Inguva

nice question, _very_ nice instant feedback on replies to question. Nice to work with you -wc

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,760 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot