Clone Issue in different project, link to parent, assign, email

[Trevan Householder_Isos-Tech-Consulting_]

Use case: 

As a JIRA Admin, I want employees to be able to submit their "Name Change" through JIRA Service Desk.  The creation of this request needs to spawn multiple issues (clones) in different projects, each of which automatically get assigned to specific people, and then email other non-JIRA users.

How is this best achieved?

[Trevan Householder_Isos-Tech-Consulting_ · Accepted solution]

I figured this out a while ago, so I thought I should post the answer in case anyone else needs this.

I went with Bob Swift's Create On Transition plugin, which is fantastic.  Here are the parameters:

In the workflow, the On Create step, I created a post function that creates an issue.

Create issue 

Conditions:

• Condition value: %original_summary%, Regex pattern: Name Change, Exact

Summary: %original_summary% 

Description: %original_description% 

Project: [PAYR] Payroll 

Issue type: Name Change (10601) 

Priority: (1) Major (10100) 

Reporter: Current user 

Assignee: Specific user (first.lastname of user) 

Affected versions: None 

Fixed versions: None 

Components: Parent issue's components 

Copy parent issue custom fields: 11207, 11115, 11500, 10179, 10180, 10197, 10198, 10255, 10258, 10261, 10263, 10264, 10268, 10270, 10271, 10272, 10274, 10286, 10287, 10288, 10289, 10290, 10291, 10292, 10293, 10294, 10296, 10297, 10298, 10299, 10300, 10301, 10302, 10303, 10304, 10305, 10306, 10307, 10308, 10309, 10310, 10311, 10312, 10180, 10197, 10198, 10258, 10264, 10270, 10271, 10272, 10273, 10274, 10286, 10287, 10288, 10289, 10290, 10291, 10296, 10297, 10298, 10299, 10300, 11100, 11113

Copy original issue custom fields: 11207, 11115, 11500, 10179, 10180, 10197, 10198, 10255, 10258, 10261, 10263, 10264, 10268, 10270, 10271, 10272, 10274, 10286, 10287, 10288, 10289, 10290, 10291, 10292, 10293, 10294, 10296, 10297, 10298, 10299, 10300, 10301, 10302, 10303, 10304, 10305, 10306, 10307, 10308, 10309, 10310, 10311, 10312, 10180, 10197, 10198, 10258, 10264, 10270, 10271, 10272, 10273, 10274, 10286, 10287, 10288, 10289, 10290, 10291, 10296, 10297, 10298, 10299, 10300, 11100, 11113

The most tedious part was getting all of the custom field IDs.

I hope this helps someone save time.

[Trevan Householder_Isos-Tech-Consulting_]

Thank you, Jobin.  

It appears that ScriptRunner will clone an issue and link to parent, but I'm not sure if it will clone it multiple times and insert into multiple different projects.  I believe it will also allow me to make the assignment.

Supposedly, Bob Swift's Create on Transition will also do this, and will create multiple clones in various projects; but I'm not a developer and I haven't been able to figure it out, yet (need more examples to work from).  

Anyone have good examples that you wouldn't mind sharing?

[Jobin Kuruvilla [Adaptavist]]

Yes. When I mentioned development, it includes scripting too ;) Unfortunately, I do not have an example to share. Hopefully someone else will.

[Jobin Kuruvilla [Adaptavist]]

The spawning of multiple issues in to different projects will surely need some custom development. Assignment might need it too but you can try to leverage automatic assignment.

Emailing non-JIRA users is another issue but plugins like jemh can probably help with that!