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
I am looking for a way to copy the team from an epic to a story/task issue upon creation. I think i have to use a json smartvalue but need help with looking up the team number first and then using that for the input to the json.
You are able to do this.
Make sure the "Team" field is available on the required screen(s).
In the automation rule use the following Edit action in the rule should contain:
{
"fields": {
"customfield_<ID>":"<Team ID>"
}
}
Example
{
"fields": {
"customfield_10001":"100"
}
}
Not all of the fields from advanced roadmaps are supported by automation rules, and I believe there are several fields called "team" in Jira...
So first thing, I recommend using this how-to article with example epics and stories/tasks to confirm the fields are supported with smart values in automation rules: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
If your field is indeed supported, you could create a rule, triggered on the story/task creation, and then copy the field from the epic parent. That how-to article will help you know the field to use and then this article will give examples of how to perform the JSON edit: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/
Kind regards,
Bill
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.
I think it is the same as this automation issue for Server/Data center version, even though you appear to be using Jira Cloud
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.