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.
I'd like to copy a cascading select from one issue to another. This requires the Advanced section in edit issue, but not sure what to put into it?
Lets assume our field is called "Sample Cascade" here. The advanced JSON block you'll need to copy this in your edit issue action is:
{ "update": { "Sample Cascade": [ { "set": { "value": "{{triggerIssue.fields.Sample Cascade.value}}", "child": { "value": "{{triggerIssue.fields.Sample Cascade.child.value}}" } } } ] } }
Here's an example rule that copies from the parent issue to all of its subtasks:
Hi
Can you please add this solution to documentation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How can I explicitly set a value for a subtask I am creating, rather than copy it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, just for anyone else.
You can simply paste in the string value of the entry into the section where the trigger is ran. You would replace {{triggerIssue.fields.....}} with "Your Value".
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.
Is it possible to inherit only the first value of a cascading field? In the target configuration, there will be a cascading field on Epic level and on Story level and the 1st field will have the same values, but not in the second field
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, can you please tell me what is wrong in my JSON? I set up copying the value of the multi-level-cascading-select field, from one task to another, but the field with my JSON is not copied.
{
"update": {
"customfield_xxx": [
{
"set": {
"value": "{{triggerIssue.fields.customfield.customfield_xxx.value}}",
"child": {
"value": "{{triggerIssue.fields.customfield.customfield_xxx.child.value}}",
"child": {
"value": "{{triggerIssue.fields.customfield.customfield_xxx.child.value}}"
}
}
}
}
]
}
}
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.
Hello guys
I want to copy 3 different select list (cascadeing) customfield from trigger issue to target issue.
How can you do this?
Help me please
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi @andreas thanks for the example!
I was trying to do something similar but if I execute this, it does not work.
{
"fields": {
"customfield_10043": "{{triggerIssue.customfield_10043.value}}",
"customfield_10043.child": "{{triggerIssue.customfield_10043.child.value}}"
}
}
It throws this error...
Error creating issueCan not instantiate value of type [simple type, class com.atlassian.jira.issue.fields.rest.json.beans.CustomFieldOptionJsonBean] from JSON String; no single-String constructor/factory method (customfield_10043)Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - customfield_10043.child
However if use your code it works just fine, I was just trying to simplify it.
{
"update": {
"customfield_10043": [
{
"set": {
"value": "{{triggerIssue.fields.customfield_10043.value}}",
"child": {
"value": "{{triggerIssue.fields.customfield_10043.child.value}}"
}
}
}
]
}
}
Is there a reason why the first one won't work or am I missing something?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are missing something, try this
{
"fields": {
"customfield_10043": {
"value": "{{triggerIssue.fields.customfield_10043.value}}",
"child": { "value" : "{{triggerIssue.fields.customfield_10043.child.value}}"
}
}
}
}
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Example with Automation Cloud to copy two cascade fields from parent to sub-tasks
[code]
{
"fields": {
"customfield_10071": {"value":"{{triggerIssue.parent.customfield_10071.value}}", "child":{"value": "{{triggerIssue.parent.customfield_10071.child.value}}"}},
"customfield_10069": {"value":"{{triggerIssue.parent.customfield_10069.value}}", "child":{"value": "{{triggerIssue.parent.customfield_10069.child.value}}"}}
}
}
[/code]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @andreas
Is it possible to inherit only the first value of a cascading field? In the target configuration, there will be a cascading field on Epic level and on Story level and the 1st field will have the same values, but not in the second field
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.