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

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

Eban Tomlinson

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?

Accepted answers

Stas9

Hi!

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

Cheers!

All comments

Joe Pitt

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.

Stas9

Hi!

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

Cheers!

Pedro Cora

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

Eban Tomlinson

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

Eban Tomlinson

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

William Crighton _CCC_

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.....

-wc

Eban Tomlinson

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

Chander Inguva

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!!

Regards

Chander Inguva

William Crighton _CCC_

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

Eban Tomlinson

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.

Eban Tomlinson

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.

William Crighton _CCC_

@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

Eban Tomlinson

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

William Crighton _CCC_

@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

screenShotOfBehaviorToRemoveComments.png

William Crighton _CCC_

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

Eban Tomlinson

Cheers!

Yana Stoliarova_l5e7vv

I used ScriptRunner Fragments (Hide)

Screenshot 2021-02-09 at 16.32.05.png Screenshot 2021-02-09 at 16.31.50.png

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration