Hi all,
I try to open an JIRA bug ticket from a JSM Incident. You see, that I'm using assets für our responsible team and on this way I can open a Bug ticket in the right JIRA Project. That works fine.
Now I would like to ask the user, if he wants open a Story or a bug. I will do it via manually triggered and ask for these 2 values; so I have input in the variable name. But what I have to write in the field issue type instead of the Bug?
Hopefully somebody have a solution?
Best Regards,
Thomas
Hi there,
You say you already have the variable? Why don't you check the content of the varable in your rule and depending on what is in it create a different issue (with different issuetype):
Something like this?
Hi,
Your message gave me the right impulse and I have to find an new way for my solution. Thanks for helping me!
Best Regrads
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I had a similar problem and solved it by adding a lookup table: key was the name of the issuetype (like the user can choose from the manual trigger) and value was the id of the issuetype (took the id from /rest/api/2/issuetype).
Then in the "create issue" action the issue type is the smart value {{mylookuptable.get(userInputs.myissuetypevariable)}}.
I did this in the cloud version (don't know if this is possible onpremise).
Hope it helps :)
Best Regards,
Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my knowledge there is no smart value for a type of issue.
So to achieve this you would need 2 rules
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.