You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all,
sure anyone can help me with this; following scenario:
In the following case it does not work:
hi @Anette Noll
Could you please elaborate more on the solution you've implemented to create an issue from B into A. Does B and A use the same workflow.
Awaiting your return
Cheers,
Karim
Hi Karim ABO HASHISH,
B and A do use different workflows. Workflow B contains Create Issue(s) postfunction. This normally works.
I have the impression that original Jira fields like description and comment, work somewhat differently in comparison to custom fields.
Therefore in the meantime I created a custom field that works as it is intended.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jira doesn't do "create issue" as part of a workflow.
You can create automations, listeners, and post functions to do it, but I'm not sure what you have done here, so I'm a bit stuck on what you have set up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.