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

Jira automation question

Mary Mark

Hi Atlassian Community,

Wondering if this is possible.

We have a source project A that contains issue: Stories and would like to move and clone to a selected project a user chooses such as: Project B, C, D

These are agile projects and they share similar templates with more or less the same fields.

We would like to on source Project A create a transition button in the workflow that allows a user to choose the project to move to, for example: Destination Project = B. Once the project is selected, then clone fields from Project A to Project B

The caveat is Project A contain fields that may not exist in other projects.

For example, Project A contains field called: Criteria and Description. Is it possible to concatenate these 2 fields Criteria + Description into the Description field in the destination project: B

Can this be achieved via Jira automation rules? Currently in the automation rule, I can only select 1 target / destination project only.

I have attempted automation rule but the concatenation piece does not work.

Please see screenshot attached.

Thanks

Mary

Accepted answers

Trudy P Claspill

Hello @Mary Mark

If you want to Clone the issue into multiple projects you will have to add a Clone Issue action for each project to which you want to Clone the issue.

To concatenate two values into one field you will need to set the destination field using smart values.

This page shows functions that you can use in smart values for text fields.

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/

Are the fields both text fields?

If so then you could try something like this:

Screenshot 2023-10-12 at 10.46.19 AM.png Screenshot 2023-10-12 at 10.48.34 AM.png

{{triggerIssue.Acceptance Criteria.concat(triggerIssue.Description)}}

All comments

Trudy P Claspill

Hello @Mary Mark

If you want to Clone the issue into multiple projects you will have to add a Clone Issue action for each project to which you want to Clone the issue.

To concatenate two values into one field you will need to set the destination field using smart values.

This page shows functions that you can use in smart values for text fields.

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/

Are the fields both text fields?

If so then you could try something like this:

Screenshot 2023-10-12 at 10.46.19 AM.png Screenshot 2023-10-12 at 10.48.34 AM.png

{{triggerIssue.Acceptance Criteria.concat(triggerIssue.Description)}}

Mary Mark

Hi Trudy, I tried that and the rule completed successfully, however on the cloned ticket I am getting the following:

Both Criteria and Description fields are multi-line text fields.

=====================================================

Action details:

This rule was configured with a project restriction. You can change this restriction in the 'Rule details' section. Only issues from the following projects or project types will be considered:

AAUS

Related issues condition

The following issues passed:

AAUS-51

Clone issue

Issues cloned successfully

AAS-42

Re-fetch issue data

Issue data re-fetched from server successfully.

Branch rule / related issues

No related issues could be found.

The new cloned ticket did not concatenate the 2 fields together into: Description field.

Please kindly advise.

Trudy P Claspill

Ah, yes, sorry.

There are single-project scoped rules and multiple-project scoped rules.

With a single-project scoped rule you are allowed to Clone an issue into a different project, but you cannot then use or operate against the issues in that other project.

The rule needs to be changed to a multiple-project rule and each of the relevant projects added to the scope of the rule.

That can be done only by a full Jira Admin from the Settings > System > Global Automation page.

When the rule is made multiple-project scoped, thereafter only full Jira Admins will be able to modify the rule, also.

And in that state, the rule will also need a Condition after the trigger to check that the trigger issues is in the one source project you want to work against. Otherwise the trigger/rule will operate against issues in all the specified projects.

Mary Mark

So the rule worked on the source issue ticket but not on the cloned ticket. In the above mentioned, I would like the concatenation to occur in the destination cloned ticket.

Thank you.

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

server

jira-software

jira-software-server