In the older JIRA UI, there was a drop down that allowed restricting of ticket comments to a specific group. We have a customer facing JIRA project and often have internal comments to post that customers don't need to see.
We could also assign a ticket and post a comment at the same time with the Assign button, which helped reduce the amount of JIRA notification emails. Now we get 2 emails, rather than one.
Anyone have any ideas on a workaround?
We spent more time switching back to the old view than any of the "new features" save us which is frustrating. I know Atlassian will eventually turn this ability off so we really need a fix.
Thanks
Hi @Carol McDonnell,
This feature is not available on the new issue view yet.
We have a feature request suggesting to our dev team to add this option on the new UI:
- https://jira.atlassian.com/browse/JRACLOUD-70149
Please, click on Vote and Watch to receive updates about the feature.
For now, it's necessary to use the old UI.
I'm sorry for any inconvenience caused by the changes on new UI.
Regards,
Angélica
Hi, is this seems to still not be supported, a YEAR LATER?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
here is the current issue tracking this. The one mentioned above was closed as a dup of this newer one. I do expect it will be coming and hopefully in 2019 - JRACLOUD-69231
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carol,
Permission Scheme is in my opinion the first place where you can make the change.
Best
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, and that would seem reasonable.
But I find it hard to believe that the permissions would change by simply switching between the old Issue View and the new Issue View for the same ticket.
Any other thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carol McDonnellThat is odd!!! I agree they shouldn't. Let me check and get back to you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks. Any help is appreciated.
My team is dreading the day JIRA removes the option to still see the old view. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carol McDonnellAre you using JIRA Service Desk or JIRA Core/Software for your project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carol McDonnellOk let me play around with both(old version and new version of the UI) then will get back to you. I may not be able to do it today but I promise to work on it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Morning @Carol McDonnell
I wasn't able to reproduce the behavior, let me as k other champions for help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carol McDonnellAre you jira cloud or server user?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is still a drop down to restrict comment visibility. By default comment visibility is set to roles. That is why, if you are not included in any role in the project, to which the issue belongs, you will not see this drop down.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carol McDonnell, Assuming you are on cloud, the new UI does (should) provide the ability to select who the comment is viewable by via a drop down. Below is what I see on my instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for the delay in responding, I was on PTO.
Fadoua - we use JIRA cloud.
Alexey - The issue is the old view vs. the new view. I can restrict comments on the exact same ticket using the old view, but this ability has gone away or is hidden someplace in the new view. And this is for all our users, Admin, etc.
Jack- The screenshot you provided looks like our old view and I agree this is how we are able to restrict comments. Here is a screen shot of the new view. The permissions drop down is gone.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carol McDonnell, you are correct. my instance had not been switched over when I originally responded.
In summary this is associated w/ the new "Bento Box" style issue view that is being rolled out. As you correctly pointed out the ability to restrict the comments as before is not present but could change at any time as they continue to make changes. If this feature is important I would recommend disabling the new view. A recent change has allowed this to occur by clicking "see the old view" in the upper right of the detailed issue view.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.