Hey Folks,
I have created a google form which creates JIRA ticket used by the sales team (They prefer creating tickets via Google form than JIRA). Since the script uses REST APIs which is authenticated using my tokens hence all the tickets which are created using google form has my name as Reporter.
I have the sales team email address in a custom field which I want to set as a reporter. Figuring our if there is any jira cloud automation exist which can update the reporter field using the email. Please note, all of these sales users have jira associated email.
Thanks in advance for the help!
Hey @Manmohan Anand
The only way I can think of to set users based on a custom field value would be advanced field editing using JSON. https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/. This requires the users ID, though, email is not sufficient.
You're going to need your initial script to run another API call before creation, and run a user search or find all users call (/rest/api/3/user/search) to get the accountID of the user you want to be the reporter. At this point, an automation becomes useless though. You now have the user ID and can set it as the reporter during your initial Create Issue /rest/api/3/issue API call.
Personally I would just make them use a JSM form. Unless this preference for google is saving the business time/money/doing something valuable that it can't, developing custom scripting to do something that's simple and built in is just creating tech debt/advanced configuration to maintain.
Hey @Ryan M Thanks for your quick response. Yes I did add the user search by their email via the REST API call (/rest/api/3/user/search) which provided the accountId which later used in the script to set the reporter. It's working as expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Journeys is a brand new feature in Jira Service Management that helps you streamline various processes in your organization that may cross multiple departments, such as employee onboarding or off-boarding that require action from different teams. ✨
Join the EAP →Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.