Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Clone completed "form" from Jira Service Management to Jira Work Management

I have a request to which I attach a form (from "Forms" in Project Settings), which is then filled out and submitted. This creates an epic in my Service Management project, which I need to duplicate/clone to a project in Jira Work Management with the filled out form.

I can't figure out how to get the data in the filled out form moved to the Jira WM project without custom fields. Is this even possible?

If it is not possible, where is the data in the completed form stored?


1 answer

@Katya Epifanova unfortunately you cannot clone a form from one project to another, this functionality does not exist at present.

I still wanted this functionality so I instead mirrored the form using text entry fields for the request type, the requester is still presented with a form to fill in, albeit put together differently in the Jira configuration.

I then created an automation rule that upon creation of the service portal ticket the description was edited to include all of the information in the description of the ticket similar to the following;

Trigger: When issue created
Condition: Request Type = Your request type
Action: Edit issue fields (description)

Form field 1
{{issue.text field 1}}

Form field 2
{{issue.form field 2}}

Form field 3
{{issue.form field3}}

A second automation rule is then present to clone the ticket as follows;

Trigger: Field value changed
-Fields to monitor : Description
-Change type : Any changes to this field
-For: Edit issue
Action: Clone issue
-Project: Destination project
-Issue Type: Destination issue type
-Summary: Destination summary
-Fields set: Fields you wish to populate

I do not use any conditions on the clone, but I might change that so that the rule on triggers on "automation by Jira" rather than a user based edit.

The reason I did the above was to avoid populating every potential destination project with additional text based fields, and to collate the information in a single, easy to read way for the request owner to complete.

I hope that's of some help if you still wanted some way to get around the inability to clone forms.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events