Loading...

XML

Word

Printable

Type: Bug
Resolution: Duplicate
Priority: Low
Fix Version/s: None
Affects Version/s: 6.1, 6.2, 6.3, 6.4
Component/s: REST API
Labels:
- affects-server

Introduced in Version:
6.01
Bug Fix Policy:
View Atlassian Server bug fix policy

(i)This applies for following REST methods:

- /rest/api/2/issue/{issueIdOrKey}/worklog
- /rest/api/2/issue/{issueIdOrKey}/worklog/{id}
- /rest/api/2/search
- /rest/api/2/issue/{issueIdOrKey}

Steps to reproduce:

1) Create JIRA user with username "user1". Please see 01 user1 details.png.

2) Put some work logs under the newly created user. Please see 02 user1 work logs.png.

3) 03 user1 work logs json.png shows that /rest/api/2/issue/

{issueIdOrKey}/worklog returns correct info.

4) Rename username to "user1-renamed". 04 renamed user1 user1-renamed.png.

5) Create new user with username "user1". Please see 05 new user1 details.png.

6) /rest/api/2/issue/{issueIdOrKey}

/worklog states that worklogs from Step 2 belong to the new user created on Step 5. Please see 06 work logs json returning wrong user.png. The Work Log comment tab shows correct worklogs association.

We reproduced this in JIRA 6.4 and 6.4.6 but I guess the same bug exists in all JIRA versions starting from 6.1 since the usernames renaming was introduced.

Attached is JIRA 6.4 hsql database.