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?
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.
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!
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?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs