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?
@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
Can I please have your update on how did you fully "disable comments" for particular issue type/s in any transition and edit screen using Behaviour.
I'm having the same question, in our case we need to disable or hide the "Comment"/"Comments" tab button from a particular sub-task/issue activity panel.
Thank you in advance.
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.....
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
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: https://answers.atlassian.com/questions/12159767/setting-comment-fields-hiddenshown-with-script-runner-plugin-not-functioning
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
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG