The Scheduler Pro 3.0 - Invalid - User who created this scheduled issue no longer exists

Daniel Booth September 11, 2013

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

Thanks

Daniel.

1 answer

0 votes
Łukasz Kreczmer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 11, 2013

Hello Daniel,

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!"?

Regards,

Lucas Kreczmer

Daniel Booth September 12, 2013

Hi Lucas

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:

Łukasz Kreczmer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 23, 2013

Hello Daniel,

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

Best Regards,
Lucas Kreczmer

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events