We have this issue:
We would like to add a feature to our users, to clone an issue and move it to another project, with a "modify screen" with some fields to edit, and automatic edit of another fields.
Now, they have to:
1. clone the issue
2. delete the value of some fields
3. move it to another project
4. edit the issue to change some fields
Our idea would be:
1. to create a new button in "more" menu called "send to another project"
2. to automatically clone, empty some fields and move it to another project
3. to automatically open the "edit screen" with some mandatory fields
How we think we could do:
1. Create the new button with ScriptRunner ScriptFragment following this documentation:
And then we have two ideas:
1. Create a "Constrained Create Issue Dialog" with the new project, and create a Behaviour to populate the create issue form with all values from the current ticket.
Pros: we can create in one step the new ticket and choose all fields pre-propulate
Cons: there are a lot of complex fields (with xray...), it's hard to populate all fields one by one
2. Create a "Custom Web Item", with a script to clone and move the ticket...
Pros: we can easily create a clone of current ticket, so no problem about the complex xray fields
Cons: We don't know how to load a screen to make the user choose some custom values for the new ticket...
For both of these ideas, we are blocked, we don't know how to do... The first one is very long to configure, because of the form behaviour on each field. The second one is not good for our UX, because we don't know how to force to edit the ticket after the clone&move.
Do you have some ideas to help us to configure this new feature?
Thank you very much!
Hello @Antoine Berry ,
Sorry, I didn't answer before.
We try to find a way to do that without paying a new plug-in... It begins to be very expensive. :)
We found a quick&dirty solution: doing a transition with the ticket we want to clone, changing some values in its fields, cloning this issue with a post-function, and reverting all the previous values of the current ticket.
So we can do everything with a transition...
For now, it's ok for us...
But thanks for this module :)
We created a new transition for all statuses to a new status "cloned".
This transition has a screen with all fields we potentially want to change during this cloning (they are hidden fields in all screens for this issue type, just "technical fields").
Then, we have a post function "Create a new issue". You need the "JMWE add-on" for this. There is no way to do that without that module, but that module is just necessary for all complex JIRAs...
Once this issue is cloned, we use the post-function called "Follow Up Transition" from the JSU app, so we can come back to the previous status.
I realize than we need two modules you maybe don't have... JMWE and JSU... Tell me if you have them and if you need more details to do so.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events