hm, that means I have to edit the workflow right?
We have like 35 issues re-entered manually to the new project, they obviously have created dates much later then the original was. I just want to run a script for each of them to change the createddate to the original one. else, I would have to stop the DB which is not a very good thing.
So you can try this from the Script Runner console... use componentManager.issueManager to get a MutableIssue object for each of the 35 issues and set the created date and store() the issue. Maybe you have to run a reindex on these issues after that, you can use the builtin reindex script from Script Runner for that.
"Deprecated" doesn't mean it's not working, only that's maybe not working in one of the next releases. A non-deprecated way to modify an issue is to use IssueService, but I'm not sure if it's possible to change the created date this way, because when an issue is created should be determined by the system...
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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