I've seen a lot of posts on this but unable to solve the problem.
In short i'm trying to use requestType in Automation. Its always coming blank.
Here's what i've tried:
Project: Team managed JSM project
Created a test automation to run as an action on the issue:
On checking the audit log after triggering - no values are returned:
One piece of advice i found is that you cannot use requestType in automation if it isn't in your edit screen. This is a team managed JSM project and as such you can't add the requestType on the edit screen.
I've checked on the project settings > request types > add request type > Fields - and request type isn't available to add.
I've just noticed we have automation working in a different project for request type that is working.
Hey @Tom Vian
in team-managed projects the request types don't behave the same as in company-managed ones. This documentation tries to explain it, but to be honest, I didn't get too much useful information from it.
In my understanding request types in team-managed JSM projects are basically the same as issuetypes. So, I'd give it a try and try to access the issuetype of the JSM issue and use this further in your automation.
I came to this conclusion by examining the JSON output when I try to retrieve the issue via REST: BASE_URL/rest/api/2/issue/ISSUE_KEY. You can replace BASE_URL and the ISSUE_KEY with your corresponding values.
Hope this helps,
Matthias.
Thank you so much Matthias - that fixed it.
I used the Issue type instead of request type and it all worked.
I've spent hours looking for that - thank you so much.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome.
That's what's the community good for - use the swarm intelligence to solve problems together.
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.