After upgrading to JIRA6 and updating our The Scheduler Pluging to version 3.0 now all our existing Issues, and any new created issues are giving the status of "Invalid" with the error message:
"01. User who created this scheduled issue no longer exists. Scheduled Issue won't be able to be automaticaly fired!"
This is extrememly frustrating and has stunted all our recurring workflows.
Can someone please advise of a fix.
We have already tried uninstalling and reinstalling the pluging as outlined in the documentation: https://confluence.atlassian.com/display/JIRAKB/The+Scheduler+plugin+update+not+working
Could you check what is the value of columns "Created By" and "Reporter" in Scheduled Issues table for entries for which you have message "User who created this scheduled issue no longer exists. Scheduled Issue won't be able to be automaticaly fired!"?
Thanks for your response.
The value in the Created By column is "N/A" and there is no column for "Reporter". When Creating the Issue I did enter a Reporter however. There was never an option to define who created the issue (in the previous version in JIRA5 this was an option).
Please see the screenshot below for your reference:
We have identified one more problem with upgrade (migration) process.
All of those probles are caused by changing the usernames policy by Atlassian. Before Jira 6.0 usernames cannot be changed. Starting from 6.0 usernames can be.
We are going to release fix for this problem on 25 October 2013
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
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