Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-4445

Ability to hide Create button based on project or signed in users group

    • 87
    • 59
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      We have a project in which we want people to create issue via the Service Desk portal however the big Create button can't be hidden so this is always in peoples face which causes them to open tickets via Jira Core which breaks workflows. Another option would be to redirect the Create button to Service desk.

          Form Name

            [JSDCLOUD-4445] Ability to hide Create button based on project or signed in users group

            Manu Mitra added a comment - - edited

            308556b7edb5 You can use that particular keyword and use as not to send email or auto delete in Automation. In my organization, after lot of struggle our Jira Admins created a different flow in that so that whenever user clicks that button it shows an error.

            I would have attached image for better understanding but unfortunately, I am not able to attach image anymore.

            I would have helped you better for get going. Sorry.

            Manu Mitra added a comment - - edited 308556b7edb5 You can use that particular keyword and use as not to send email or auto delete in Automation. In my organization, after lot of struggle our Jira Admins created a different flow in that so that whenever user clicks that button it shows an error. I would have attached image for better understanding but unfortunately, I am not able to attach image anymore. I would have helped you better for get going. Sorry.

            This causing users to select the incorrect request type within my organizations. Because of this, automations are sending tickets to the wrong queue and causing a giant headache.

            Ronald Kaforey added a comment - This causing users to select the incorrect request type within my organizations. Because of this, automations are sending tickets to the wrong queue and causing a giant headache.

            Mohan Rao added a comment -

            forms functionality is not working

             

            Mohan Rao added a comment - forms functionality is not working  

            For us the biggest reason we do not want users to submit issues directly in a service project is that by bypassing the portal UI the user is not presented the relevant KB articles which might deflect the ticket.

            Rick Westbrock added a comment - For us the biggest reason we do not want users to submit issues directly in a service project is that by bypassing the portal UI the user is not presented the relevant KB articles which might deflect the ticket.

            Manu Mitra added a comment - - edited

            @Jim Bren,

            I am not sure if it helps or useful because it uses one complete workflow.

            --> Create a Request type as "Task" or whatever is avalaible.

            --> Click on Project Settings in the Service Desk Admin

            --> Click on Project Automation

            --> Create a Rule (as below)

            You can also set Transition the issue as Delete. So it will never creates an issue.

            I work for a company, so I cannot provide more information but certainly will help if I have that software.

            I hope it helps.

             

            Manu Mitra added a comment - - edited @Jim Bren, I am not sure if it helps or useful because it uses one complete workflow. --> Create a Request type as "Task" or whatever is avalaible. --> Click on Project Settings in the Service Desk Admin --> Click on Project Automation --> Create a Rule (as below) You can also set Transition the issue as Delete. So it will never creates an issue. I work for a company, so I cannot provide more information but certainly will help if I have that software. I hope it helps.  

            Jim Bren added a comment -

            @Manu Mitra, would you mind sharing a screenshot of the automation? Sounds like a decent work around.

            Jim Bren added a comment - @Manu Mitra, would you mind sharing a screenshot of the automation? Sounds like a decent work around.

            Manu Mitra added a comment - - edited

            @Jim Bren I know right?

            I have created automation and made that create button useless and an email is sent to them stating "No one is gonna work on this request."

            Manu Mitra added a comment - - edited @Jim Bren I know right? I have created automation and made that create button useless and an email is sent to them stating "No one is gonna work on this request."

            Jim Bren added a comment -

            I imagine since this request has languished since 2017, it is pretty unlikely to get done. It'd be nice if you would say no instead of pointing us to a dead feature request. 

            Jim Bren added a comment - I imagine since this request has languished since 2017 , it is pretty unlikely to get done. It'd be nice if you would say  no instead of pointing us to a dead feature request. 

            When I press the Create button, the screen created by the form's functionality does not load.

            Required fields set in the form are not displayed as input fields, resulting in inappropriate requests being submitted.

            Masayuki Abe added a comment - When I press the Create button, the screen created by the form's functionality does not load. Required fields set in the form are not displayed as input fields, resulting in inappropriate requests being submitted.

            Yeah we are getting a lot of problems because when JSD agents create issues they usually forgot to set a lot of our custom fields used for our workflows and KPI's

            Mark Elkomos added a comment - Yeah we are getting a lot of problems because when JSD agents create issues they usually forgot to set a lot of our custom fields used for our workflows and KPI's

              Unassigned Unassigned
              08aa4958c2cd ken_becker
              Votes:
              56 Vote for this issue
              Watchers:
              58 Start watching this issue

                Created:
                Updated: