For example, if I create a child issue, I would like some of the custom fields to autopopulate from the epic issue so people don't have to manually re-enter them.
Hi @erica_dahl , thanks for your question.
I would use an automation for this.
You can use a rule like this in the automation library as an example / to get some ideas. Basically here, we're creating a series of subtasks and you could copy in the same moment, the values from the custom fields in the parent issue
https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112180/26549811
The other possibility would be to use custom field contexts and default values. https://support.atlassian.com/jira-cloud-administration/docs/edit-a-custom-field-context/ .
If, for example, in a certain project, the custom field is only used in one issue type and should be populated with a default value, you could set a custom field context for the project / issue type combination and set a default value. For example, if you have a radio button with a yes or no choice, you could set it as a default to yes and then people have to change it to no.
Anyway, I hope this helps you. Please write again here if you have any questions or doubts.
Best wishes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.