Yes, you can solve almost anything with Script Runner (in JIRA, Bitbucket or Confluence at least), but I thought that this was more of a one-off correction than something you'd do a lot. I'm not sure there's a good use-case for doing this a lot, it feels a bit like a broken process.
But, I suspect you can still do it. The latest versions of SR allow you to insert simple hooks into the interface as buttons. I have only used them a bit, and I don't know if they can do the "input field" bit, but they can certainly trigger the scripts, and with a script, you can go read all sorts of stuff as input. So I know you can get close.
(Apologies if this feels like an advert - I do work for Adaptavist, SR is one of our flagship products, and hence I use it a lot. This really is one where SR feels right, and if I didn't work here, the only change I'd make to this answer would be to drop this comment about working here!)
And potentially destroy your installation. SQL on a JIRA database is to be avoided at all times. Always use the API. If you must use SQL, plan to shut it all down and take a backup before risking it, and then factor in the time for a full reindex afterwards.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot