when creating an issue, possible to default reporter to team lead?

[Jorge Cañaveral]

hi, im trying default settings so every time we create a ticket, reporter is set to our IT manager opposed to whoever creates the ticket. 

I've been playing around in configuration but dont see this option, is it possible ? 

[Gomez, Daniel]

Yes, you can use a post function in Jira Cloud to automatically set the reporter of an issue to your IT manager when a new ticket is created. Here's how you can achieve this:

• Navigate to your Jira project:
  • Go to your Jira project where you want to apply this default setting.
• Access Workflow:
  • From the project settings, go to "Workflows."
• Edit Workflow:
  • Edit the workflow associated with your project.
• Add a Post Function:
  • Find the transition that occurs when an issue is created (usually the "Create" transition) and add a post function to it.
• Select the Post Function:
  • Choose the post function called "Update Issue Field."
• Configure the Post Function:
  • Configure the "Update Issue Field" post function to set the reporter field to your IT manager.
• Specify the Reporter:
  • In the configuration screen, find the field for "Field to Change" and select "Reporter."
  • Set the "Type of Function" to "Set Field Value."
  • In the "New Value" field, enter the username or name of your IT manager.
• Save the Workflow:
  • Save the changes to your workflow.

Now, whenever an issue is created, the workflow will automatically update the reporter field to the specified IT manager. Keep in mind that you need the necessary permissions to edit workflows and that you have the correct username or name for your IT manager.

[Jorge Cañaveral]

Hi Daniel, thanks for the response, appreciated! 
however im stuck on step two "Access Workflow: From the project settings, go to "Workflows."  I dont see that on my screen unless im on the wrong project settings. I know I have admin access. screenshot attached 

[Gomez, Daniel]

If you're not a site admin, you may need to request assistance from your Jira administrator. For example, an administrator group with all admin permissions except site admin can do it. Project admin is not enough.