Hi @eran vaks Welcome to the community,
Can you please explain your requirement in brief like what action should update or set the certain value for the custom field?
This this achievable using automation rule but based on the requirement we need to use the correct trigger.
Parent is only valid for a standard issue type like story to a sub-task issue type like Sub-task. If you created a new sub-task type for something like Sub-task Bug or Defect or something like that, then you could get a a parent to child relationship.
Here's what we do. If a bug/defect is found in testing, if the problem that was found keeps us from deploying the code, then we create a Defect card, which for us is a Sub-task issue type. Then we prevent any cards from moving to done if there are open sub-tasks (i.e. Defects in this case).
If the problem will not prevent the code from being deployed, then we create a Bug, which is a standard issue type and is placed in the Backlog to be fixed at a later point.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events