I cannot find an example from JMWE that is close to what I want to do. (I am not a programmer so I do a lot by example and error.)
I have bugs and features in one project and when someone hits a step in the workflow they have to decide if they want to copy the bug or feature to a different project. I want to use create issue once to clone the issue. The bug should be created/cloned as a bug and the feature should be created/cloned as a feature. The issue types are the same across the projects.
What would be the right syntax to detect a bug issue type and assign the new issue the bug issue type?
in the Create Issue(s) post function, under Destination -> Issue Type, select "Calculated" and use this as the value:
{{ issue.fields.issuetype.id }}
Hi @Sigrid Schoepel ,
Based on what you have indicated here, I have to wonder if using automation might be a better solution for you. The one unknown for me centers around your "...they have to decide if they want to copy the bug or feature to a different project.". What is the criteria for making this decision? When they decide to proceed with the clone? further, might I inquire as to what is driving the clone altogether? The reason I ask is that it might help me form the best answer to your question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us June 26, 11am PT for a webinar with Atlassian Champion Robert Hean & Loom’s Brittany Soinski. Hear tips, stories, and get your burning questions answered. Learn how Loom makes training and enablement easier. Don’t miss it!
Register todayOnline 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.