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; } } }

Is it possible to copy a custom field value into the default Priority field?

Alex Degregori

Hey!

I was curious if it is possible to copy a custom field value (single choice dropdown) into the default Priority field?

I've looked at Automation, but there seems to only be the option to set a value depending on if there are changes in the trigger, not copy the value from my custom field into the default Priority field. Using the Additional fields section in Automation, is there a way to connect the two?

I'd like to point out, the custom field does have the same "values" as the default Priority field: lowest, low, medium...etc.

Accepted answers

Ste Wright

Hi @Alex Degregori

There might be - but isn't "copy to" and "set value based on" the same thing?

I'd think the easier method here would be:

Trigger: Field Value Changed - based on <<Field Name>>
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals Highest
Action: Edit Issue - set Priority to Highest
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals High
Action: Edit Issue - set Priority to High
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals Medium
Action: Edit Issue - set Priority to Medium
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals Low
Action: Edit Issue - set Priority to Low
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals Lowest
Action: Edit Issue - set Priority to Lowest

^ This should give you the same result

Ste

All comments

Ste Wright

Hi @Alex Degregori

There might be - but isn't "copy to" and "set value based on" the same thing?

I'd think the easier method here would be:

Trigger: Field Value Changed - based on <<Field Name>>
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals Highest
Action: Edit Issue - set Priority to Highest
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals High
Action: Edit Issue - set Priority to High
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals Medium
Action: Edit Issue - set Priority to Medium
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals Low
Action: Edit Issue - set Priority to Low
Branch: Current Issue
Condition: Issue Fields Condition - <<Field Name>> equals Lowest
Action: Edit Issue - set Priority to Lowest

^ This should give you the same result

Ste

Rawlo Smith

Hello @Ste Wright

Can you please elaborate where I would put these Trigger, Branch, and Conditions? I don't recall seeing such options anywhere in any of the configuration settings. I would love to use your solution, I just don't know where to apply those steps.

I want the priority calculated and set based on details added when the ticket is created.

Right now via JSU or JMWE I can copy to Priority field on workflow transition and it works but only on transitions after the issue has been created so all the new issues are missing the priority level. I have never gotten it to work in the create transition (calculated priority will populate into other fields upon create but not in to the Priority field).

Thanks!

David Fischer

@Rawlo Smith there's absolutely no reason for JMWE not being able to set the Priority using a post function on the Create transition. Can you share your attempt with JMWE?

Rawlo Smith

@David Fischer For JMWE, I am using the post function option "Copy value from field to field (JMWE app)" I have tried moving it to all possible positions around the the original 4 default post functions (I have done the same thing with Copy Value from Other Fields (JSU)).

I am copying a value from a calculated field. Depending on the position in the post function list, I either end up with Priority not being set at all (blank) or being set to the default value rather than value I am trying to copy into the field.

I can copy that calculated field into Comments upon create so I know the calculated result is available.

I can also copy the calculated field to Priority if I do the same post function between the first and second workflow step after "Create" (Open and In Progress respectively) rather than between Create and the first workflow step (Open). So I don't believe it is not a field compatibility issue.

I am working on Server v8.5, so maybe I need to get Jira up to the latest version.. Looking around I see the Trigger, Branch, Conditions options you listed above look like they are either part of the cloud offering so maybe that is why I have not seen them, is that correct?

Thank you,

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation