You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @ani rosita,
It's not possible to create a Request Type "Hidden from Portal" directly in JIRA Service Desk.
You need to create a new Request Type With the same Issue Type and after the request is being created in JIRA you can change the Request Type to the "Hidden from Portal".
Create a new one of this "Present" Request Type with the issue type "Solicitud de servico":
I have a Hidden from portal Request Type "Email" with the same Issue type:
Then I go to the agent view and change the Request Type:
I hope this help to solve your problem.
Adrián Plaza [DEISER]'s reply to
You need to create a new Request Type With the same Issue Type and after the request is being created in JIRA you can change the Request Type to the "Hidden from Portal", worked for me.
I then created a rule that looks like the one below.
Issued created via email are labeled 'created-via-email' which makes the query work. The Customer Request Type used is Email Ticket and is hidden in the projects portal.
You can raise a hidden request via the Create Issue link which you'll find in the Quick links gadget, in the dashboard (you can then add a shortcut to this page from your project sidebar for all agents to use) It looks different to the way you raise via the portal, but means you don't have to raise it as one request type first.
I hope that helps someone else looking to do this - it took me a while to realise it.
You can only keep the tickets hidden from customers by not adding them in as a reporter/organisation etc. So for us we have a number of issue/request types that need to follow a different workflow but realistically the customer will not know to pick these via the choices in the portal. So if they raise a ticket as Support, then we realise once investigated that it's a particular type of support (e.g. needs a code change to the software), we can move the ticket into that alternative issue type to pick up the correct workflow (allowing for all the quality checks required etc.). As long as the customer is still noted on the ticket (reporter etc.) they will still see it's progress via their online portal.
We do have other tickets - such as Internal incidents that affect customers but we do not want them to see all the details, so in this case we just raise the ticket against our company instead and use an alternative field to show which customer may be affected. Again this ticket type is hidden from the front portal so that customers don't accidentally raise their tickets against it.
I hope that helps.