REST call uses wrong username when username has been renamed

[Devid Verraes]

Steps to reproduce:

1. Create user with username xyzabc
2. Rename the username to abcxyz
3. Go to the scheduler project tab
4. Create a new scheduled issue
5. The project field and issue type field remain empty

=> The user cannot create a scheduled issue

In chrome when you check the network connections, you'll see that a rest call is made with the old username and this doesn't return any result

<jira_host_name>/rest/thescheduler/1.0/project?userKey=xyzabc

I disabled and enabled the plugin, but this didn't have any effect.

[Łukasz Modzelewski]

Hi Devid,

Thank you for reporting this issue.

We are investigating this right away.

Cheers,

Łukasz

[Devid Verraes]

Hi Lukasz,

There seems also another problem, I thought the rest call (/rest/thescheduler/1.0/project?userKey=office06) didn't give a reply because the user name was wrong. But it turns out that it only gives a reply when the user has jira-administrator rights. If not, then you'll get the following result:

{"errors":[{"project":"Invalid Project ID"}]}

I checked all permissions of the user:

• User has project admin permission in the project
• User was added in the Manage access section of the Scheduler plugin as allowed user.

I don't know if it matters, but we are using a permission scheme with only project roles and no groups.

Br,

Devid

[Łukasz Modzelewski]

Thank you for additional details.

We also noticed this and we are working on fix.

[Łukasz Modzelewski]

Hi Devid,

Again thank you for reporting this.

We have fixed this issue in today's release of version 5.0.8.

Please upgrade plugin.

Cheers,

Łukasz