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

How to copy domain to a custom field

SunilKumar.Shangishetty

I'm trying to copy the Domain name to a custom field every time when the issue is created.

Can someone help me with this.

Accepted answers

Mykenna Cepek

The easiest way to accomplish this would be to use Automation in Jira.

Specifically, you'll want a rule that:

Starts with the "Issue Created" trigger
And then uses an "Edit Issue" action to Copy the Domain field value to the other custom field (three-dots menu > Operations > Copy From).

Here's a link to get started with Automation (in case you haven't used it before):

https://www.atlassian.com/software/jira/guides/expand-jira/automation

Be aware that there are limits on Automation usage with the Jira Free plan:

https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

In particular, note the 100 "rule executions" per month limit for the Free plan.

_ _ _ _ _ _ _ _ _ _ _ _ _ _

An alternative solution is to set a Post Function on the Create step in the Workflow:

Edit the workflow for the project.
View the workflow as a Diagram (not as Text).
Click on the "Create" transition (coming out of the circle).
Click the "Post Functions" hyperlink in the pop-up.
Click "Add post function".
Select "Copy Value From Other Field".
Click "Add" to add the new post function to the Create transition.
Be sure to "Publish Draft" so that your new workflow is saved and deployed.

This approach is a bit more hidden, but there is no "execution limitation".

All comments

Mykenna Cepek

The easiest way to accomplish this would be to use Automation in Jira.

Specifically, you'll want a rule that:

Starts with the "Issue Created" trigger
And then uses an "Edit Issue" action to Copy the Domain field value to the other custom field (three-dots menu > Operations > Copy From).

Here's a link to get started with Automation (in case you haven't used it before):

https://www.atlassian.com/software/jira/guides/expand-jira/automation

Be aware that there are limits on Automation usage with the Jira Free plan:

https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

In particular, note the 100 "rule executions" per month limit for the Free plan.

_ _ _ _ _ _ _ _ _ _ _ _ _ _

An alternative solution is to set a Post Function on the Create step in the Workflow:

Edit the workflow for the project.
View the workflow as a Diagram (not as Text).
Click on the "Create" transition (coming out of the circle).
Click the "Post Functions" hyperlink in the pop-up.
Click "Add post function".
Select "Copy Value From Other Field".
Click "Add" to add the new post function to the Create transition.
Be sure to "Publish Draft" so that your new workflow is saved and deployed.

This approach is a bit more hidden, but there is no "execution limitation".

SunilKumar.Shangishetty

Hi Mykenna,

Thanks for the quick response. we don't have a field called Domain, I want to copy the domain from the reporter field to a custom field.

Mykenna Cepek

I see. Then the "Workflow - Post Function" approach will not work for that.

Automation can do this, though. You'll do what I mentioned above, but the "Edit Issue" action is just a pinch more complicated.

I created the rule below to test it. This rule copies the assignee email address domain (everything after the @ in the email) to the Description field. You'll want set it to your custom field instead.

I have the action component selected in the rule so you can see the Smart Value notation used to extract the email address and parse out the domain.

Screen Shot 2020-12-09 at 5.14.57 PM.png Important notes:

If the assignee is blank, the domain will also come back blank.
I'm not sure how you're assuring that the Assignee is set when the issue is created. If this automation runs BEFORE the Assignee is set, then the rule will appear to succeed, but the domain will be blank.
You might also consider a second rule to trigger this same action when the Assignee field changes. I assume you'd want to keep this custom field in sync, in case the issue is reassigned.
The 100 rule executions per month limit on the Jira Free plan is still in play here.

SunilKumar.Shangishetty

Thanks for your response Mykenna.

I have tried the automation but I'm getting the error. Please check the attachment for the errors and automation.

And I'm trying to pull the domain from the reporter field, not from the assigned field.

Screen Shot 2020-12-09 at 4.02.30 PM.png

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-core

jira-core-cloud