Auto ticket creation in another project using field values

[Lakshmi CH]

Hi Team,

 Please let me know if you have any suggestion to achieve this.

Trigger Event:

Ticket Project = "Trading Partner Development" (MD )

Issue Type = "FI Task"

Event: Status transition to "Regression Testing in Process"

Check that mandatory fields have data (to source from)

• TPD Document Type cf[31714]
• Summary of Changes cf[17000]
• Scheduled RM Install Date cf[10706]
• Map Name cf[10211]

If any of the above fields do not have data, fail the downstream process and send an email to the Assignee noting the failure and reason

Downstream action:

Create new ticket project = "Regression Testing" (RT)

Issue Type = "Task"

Status = "Open"

Source below information from the MD Task (trigger event)

MD field	RT field	Notes
'Hub Name' cf[10208] and  'TPD Document Type' cf[31714]	Summary	Both fields should be used to create the Summary with format like "Hub Name / TPD Document Type"
Summary of Changes cf[17000]	Summary of Changes cf[17000]	n/a
Scheduled RM Install Date cf[10706]	Scheduled cf[18902]	n/a
Map Name cf[10211]	Map Name cf[10211]	n/a
New Map Name cf[33703]	New Map Name cf[33703]	Optional - only source if (###) has data
Datatype UID cf[33708]	Datatype UID cf[33708]	Optional - only source if (###) has data
Escalation? Cf[10500]	TPD Ticket Escalated cf[33121]	Optional - if (###) = Yes, (###) = Yes Else (###) = null
Parent	Issue (link)	Linked Issue = 'relates to' and issue = parent ticket's number

[Bill Sheboy]

Hi @Lakshmi CH 

Do you have the marketplace add-on for automation rules for server:

https://marketplace.atlassian.com/apps/1215460/automation-for-jira-server?hosting=server&tab=overview

If so, you can automate this process by creating an automation rule.  Please see this documentation to help you get started:

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

Best regards,

Bill