nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation issue

Patrick Cigana

Hi all,
I am having an issue with a new field tab I have set up. Basically, I have one Jira board that copies to another (sales-onboarding). I created a new mandatory field in the sales board which is not causing any issues in the automation audit log. When it gets copied from one board to the next (once it is completed) I have 'Issue condition' passed and then 'create issue' 'error creating issue' 'custom field is required' and then 'create issue' 'error creating issue' 'custom field is required'. I am still a rookie at this and learning. In the original sales board when the issue is cloned I have the 'custom field' 'copied from current issue'. Any advice would be great. Thanks in advance.

Accepted answers

Bill Sheboy

Hi @Patrick Cigana

For a question like this, please consider posting images of your complete automation rule and the audit log details showing the execution that doesn't work as you expect. That will provide context for the community to offer ideas. Thanks!

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Patrick Cigana

Kind regards,
Bill

Patrick Cigana

Thanks for that. Will do.

Patrick Cigana

Screen Shot 2022-04-20 at 8.18.32 am.png

Patrick Cigana

This is an example of the automation error I get in the onboarding board once the issue has been cloned over.

Bill Sheboy

Hi, Patrick.

Please try to stick to one thread in responding; otherwise people may think there are multiple answers to the question.

For that error message: cloning issue links is not supported yet for an automation rule. Here is the suggestion to add that: https://codebarrel.atlassian.net/browse/AUT-2133

I believe the work-around is to clone the issue, and then use a branch on created issue to add them...although when you clone into a different project that means the rule must be defined as global/multi-project in scope.

Also I noted...you referenced the smart value {{fieldChange.fromString}} and with a transition trigger I expect that will only contain Status information...unless you have a transition page/screen in your workflow. What I do not know: does the transition occur (and so fire the rule) before or after that page/screen is completed. Perhaps write {{fieldChange}} to the audit log to confirm. If in fact it is after the page/screen then {{fieldChange}} is a list of changed fields and not just one.

Thanks,
Bill

Patrick Cigana

Thanks for your assistance Bill.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud