Hi all,
We would like to exclude some confidential information included in the service requests to avoid to support team being able to see it.
This information is captured from a custom field.
Can we prevent them from seeing this information on the ticket?
Regards,
Carlos Quintana
The solution proposed doesn't work.
I am sorry, but I tested the solution in Full and it indeed worked.
Seems there are some misconfiguration in 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 cannot hide specific fields based on security out-of-the-box in Jira, you would need to get an app that app that allow you to do that. If you go to the marketplace and search for field security you will find apps that can do this for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Carlos Giovanny Quintana Corredor
Could you please clarify if by "support team" you mean the Service Desk Team users that resolve the issues?
You can hide the field from the screen of the ticket details, however that field will still be available in CSV export and in filter results.
Regards,
Eugenio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Eugenio,
Thanks for your prompt response.. and yes... I am talking about Service Desk Team.
Could you please guide me on how to do it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Carlos Giovanny Quintana Corredor
Greetings from Brazil!
Sure, you can achieve it by customizing the screen. In a nutshell:
On the screen of Step #1, the field should be available.
On the screen of Step #2, remove the field you want to hide.
Regards!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Eugenio Onofre . Jut to clarify, my request is to prevent them (service Desk team) from seeing this information on the ticket.
The goal here is to hide those fields on their dashboard view. We don't want to allow them to see this info once they receive the ticket.
So, what you mean is remove those fields from view and edit screens?
Removing them from those screens the service desk team won't be able to see that information in the ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Carlos Giovanny Quintana Corredor
This is correct, but please bear in mind that if they EXPORT to CSV or search for issues using JQL, they may access the values of the field.
Another option would be to use a Marketplace plugin, such as:
https://marketplace.atlassian.com/apps/1226228/protected-fields?hosting=cloud&tab=overview
Regards,
Eugenio
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.
The Service Desk team continuing seeing that information
By the way. It is possible to test this without creating a new ticket?
As you can see the fields were removed from the screen edit and view
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carlos,
You have to properly assign the screens in your Screen Scheme.
when you edit it, you will have the ability to assign different screens for Create, View and Edit actions.
about testing without creating a new ticket, yes, you can do it by checking an existing ticket.
I again reinforce that although it hides the field from the ticket screen, users will still be able to get this information in filters or CSV export.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Eugenio Onofre I'm fine with the restriction of they can see it in filters or CSV.
They usually don't use those options.
The main goal here is they can't see it on the ticket.
First of all, I don't understand why do we have so many screens
Second, based on the previous pictures it should be the (7) screen and those fields were removed from the edit and view screens but the service desk team continues seeing the information.
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.
@Carlos Giovanny Quintana Corredor
I am helping as much as I can :)
Please find my comments below:
First of all, I don't understand why do we have so many screens
This is something managed by the Jira Administrators. Usually when a new project is created by using default configuration, additional screens are created
Second, based on the previous pictures it should be the (7) screen and those fields were removed from the edit and view screens but the service desk team continues seeing the information.
You have to edit the SCREEN SCHEME being used by the project. A screen scheme configuration looks like below:
The "Edit" button in front of each action will allow you to assign the appropriate screen. In case the "View" operation is not listed, use the "Associate an issue operation with a screen" button.
I strongly recommend reading out the Jira Admin documentation to be familiar with the main concepts:
https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/
https://support.atlassian.com/jira-cloud-administration/docs/manage-screen-schemes/
Once you are able to link the screen you created with the View action, this will resolve your request :)
Please do not forget to VOTE on the solution and mark as ACCEPTED if it resolves your issue.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Eugenio Onofre I know that you are helping me and I really appreciate your effort.
about the steps
Edit Screen Schema ....once I click on edit
This is what I am seeing
Is that what I should see?
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good morning @Eugenio Onofre
About the last pictures that I sent to you...do you have any other recommendations?
I don't understand why the service desk team keeps seeing that information on the ticket if based on your recommendations that information should be hiding from them.
I will be attentive to your comments
Regards
Carlos Quintana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carlos Giovanny Quintana Corredor
You should select the screen where you hidden the field from as the VIEW screen.
But you need to make sure this is the Screen Scheme being used by the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Eugenio Onofre ... Sorry Eugenio, I couldn't find why is not working.
All seems to be set as you have proposed but the service desk team continues seeing that information in the ticket.
Any other piece of advice will be appreciated.
I can send more pictures if you want of the current configuration, please don't let me alone with this.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carlos Giovanny Quintana Corredor
I am sorry but I have no additional steps to provide.
All the steps I have provided are the ones you have to follow in order to hide the field from the view of the Service Desk Resolution team.
I strongly advise reading the Jira Administration content and documentation available to better understand how screens and screen schemes work.
The only thing I could suggest additionally at this time is you to provide screenshots of:
With these screenshots I may be able to assist further, but it is imperative at this time to have good understanding of the Jira Administration features.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Eugenio OnofreThank you once again for your patience and willingness to help.
Here are the screenshots.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I need to see the name of the Screens and Screen Schemes.
Please update all screenshots to show the name of the schemes.
This seems to be an issue with a wrong Screen/Scheme/Project linking.
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.
Can you provide the Screenshot for Issue Type Screen Scheme and the Project Configuration where it shows the scheme being used?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I used this reference to take the screenshots
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carlos Giovanny Quintana Corredor
I am sorry but I am afraid I will not be able to assist any further in here.
You need to make sure that:
On the best hopes to have helped.
Regards,
Eugenio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Eugenio Onofre just to confirm. The pictures that I sent are ok?
Second. if the pictures are OK... it means that is a BUG in Jira? because it is, we need to report it.
Third...thanks a lot for all your help.
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.