How to configure a workflow transition screen

[Dean Losurdo]

When we transition a ticket status in one of our projects to another status named Publish to Busienss we have configured this so that when it reaches this point an automation creates a ticket in a different project and copies all the custom fields across from this ticket to the new one.

However despite the custom fields being available in both projects and are added into both issue types for some reason the automation does not copy some information in two of the fields. I have compared it with other fields I have created and there is really nothing different about these both. Is there something that can be causing this?

I did also notice that when I transition the status to Publish to business and a window appears the field does not seem to appear on the window where this can be found in the screenshot below

[Trudy Claspill]

Hello @Dean Losurdo 

What are the Types for the source and destination projects? You can find that information in the Type column on the "View all projects" page under the Projects menu.

What are the field types of the fields that are not copying over?

You said it is not copying "some" of the information from the fields. Can you provide more specific examples of the source data and what ends up getting copied?

Can you show us the details of the rule step where you are copying that data?

To add a field to a transition screen you will need to identify the screen used in the transition and then update that screen. You can find the screen associated to a transition from viewing that transition's information from the Workflow Editor screen. Then you can change the fields on that screen from Jira Administration > Issues > Screens. 

[Trudy Claspill]

In the Audit Log information you provided on October 2 it shows No Actions Performed.

In those cases, the new issue is not being created when the rule runs.

For the specific execution you showed, PAC-8459 was the issue that triggered the rule, but it did not meet the second (CR - Employee Number starts with C) of the two conditions you specified so the step to create an additional issue was not executed.

If no new issue is created, then certainly data could not be copied from the source issue.

In an earlier response on Sept. 28 you indicated that PAC-8474 was an issue that triggered execution of the rule. However, the Audit Log screen you shared shows the status of all rule executions since Sept. 27 has been No Actions Performed, which means that rule has not created any new issues.

If new issues are being created by Automation, it is not being done by that rule.

[Dean Losurdo]

So the project types are both service management projects and the field types are both single line text fields

the custom fields that are not copying across are named:
CR - Contractor Company
Personal/Work email (Not a CR one)

As seen in the screenshots below this is what data is in the field but when it gets copied to the next ticket nothing come through. I have also attached a screenshot of the automation

This is the ticket created from the automation. You can see the corporate development and manager fields have copied across but the two mentioned before havent.

---

---

[Trudy Claspill]

Are the source and destination projects Company Managed or Team Managed? That info will display at the bottom of the navigation panel on the left when you are viewing the project information.

Are the fields to which you are copying the data also single line text fields?

Can you show us the full automation rule? What information is in the Audit Log for the execution of the rule?

[Dean Losurdo]

Both projects are both listed as company-managed projects

Yes they are, I have also tried using long text fields but the same issue occurs. But still the other fields don't come through

I have attached a screenshot of the automation rule for you. The highlighted rule in the audit log is the one for the ticket seen in the screenshots above.