I have a Cascading Select custom field that I would like to have subtasks inherit on creation. I have tried using both JMWE to Set Field Value from Parent and JSU to Copy Value from Other Field as part of the Create Transition in the workflow. Both produce the same inconsistent result, namely, they don't always pick the right cascading select combination for the subtask.
My custom field has values like:
My test parent issue has this field set to BAU - Upstream, BUT the subtask creation invariably picks 2012 - Upstream. When I change the field value on the parent to 2013 - Project A, it successfully creates a subtask with the correct field value.
Has anyone seen similar behavior or have suggestions for alternatives or work-arounds?
We're running JIRA 6.0.8 with JMWE 3.3 and JSU 1.4.9.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs